Connect Any AI Tool to PlantDemand MCP: Client Setup Guides

The PlantDemand MCP server works with any client that supports remote HTTP MCP servers and custom request headers. This page lists the clients with detailed setup guides. If your client supports the spec, the configuration is always the same: point it at https://plantdemand.com/mcp and add a Server-Api-Key header.

Available client guides

Anthropic

  • Claude Desktop — The most common starting point. Edit the desktop app’s MCP configuration JSON and connect in under five minutes.
  • Claude Code — Anthropic’s terminal coding assistant. Add the PlantDemand MCP server through the CLI configuration.

Developer-focused IDEs and agents

  • Cursor — Add the MCP server to Cursor’s settings to use it inside the IDE chat.
  • Replit Agent — Connect Replit Agent to the PlantDemand MCP server for in-Repl plant data access.
  • Kiro — Amazon’s spec-driven AI IDE supports remote MCP servers with header authentication.

Microsoft

  • Microsoft Copilot Studio — Add the MCP server as a tool inside a Copilot Studio agent for use across Microsoft 365.
  • Azure AI Foundry — Connect Foundry agents to PlantDemand MCP for enterprise deployments on Azure.

OpenAI

  • ChatGPT — Connect MCP through the ChatGPT connector or developer mode (availability depends on your plan).

Other MCP clients

The configuration pattern is the same for every spec-compliant client. If your client supports remote HTTP MCP servers, use this template:

{
  "mcpServers": {
    "plantdemand": {
      "url": "https://plantdemand.com/mcp",
      "headers": {
        "Server-Api-Key": "${PLANTDEMAND_SERVER_API_KEY}"
      }
    }
  }
}

If your client only supports local stdio MCP servers and not remote HTTP, you will need a small bridge. The most common option is mcp-remote or a similar relay.

Generic checklist before you connect any client

  • You have an active PlantDemand account with at least one plant configured
  • You have generated a Server-Api-Key (see SOP 4.1 in your customer documentation)
  • Your client supports remote HTTP MCP servers
  • Your client supports custom request headers (specifically Server-Api-Key)
  • The curl examples in the quickstart work end-to-end from your network

Where to go next

This guide is part of PlantDemand’s asphalt plant software hub for asphalt plant operations, scheduling, and sales management.