Connect Replit Agent to the PlantDemand MCP Server

Replit Agent supports MCP servers through the Replit MCP configuration. Once connected, the agent can pull plant, order, and material data from PlantDemand while building integrations, reports, or internal tools inside a Repl.

Before you start

  • An active PlantDemand account with at least one plant configured
  • A Server-Api-Key generated for your account (see SOP 4.1)
  • Replit Agent installed and working with at least one MCP server already (or this is your first MCP setup — that is fine too)
  • Verify the curl examples in the quickstart work from your network before configuring the client

Configuration

Add the following configuration to Replit Agent:

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

Step-by-step setup

  1. Open your Repl and add PLANTDEMAND_SERVER_API_KEY as a Secret in the Replit Secrets pane (left sidebar > Tools > Secrets).
  2. Open the MCP configuration for your Repl (typically .replit/mcp.json or via the Replit Agent settings panel — check the latest Replit documentation as the path may change).
  3. Add the PlantDemand entry shown above to the mcpServers object.
  4. Restart your Replit Agent session. The PlantDemand tools should appear in the available tool list.
  5. Test with a prompt like “list my PlantDemand plants” or “show this week’s schedule for plant 14”.

Verifying the connection

After connecting, ask Replit Agent:

“List the plants I have access to in PlantDemand.”

If the assistant returns a list of plants, the connection is working. Try a follow-up:

“What is on the schedule for plant [your plant ID] tomorrow?”

Troubleshooting

  • MCP configuration not recognized: Replit’s MCP support evolves quickly. Check the Replit documentation for the current configuration file location and format if the path above does not work.
  • Agent does not call PlantDemand tools: Mention PlantDemand explicitly in your prompt and ensure the agent has been restarted since adding the MCP server.
  • Secret not exposed to MCP: Confirm the secret name matches exactly (case-sensitive) and that the Repl has been restarted.

Where to go next