Connect an AI assistant (MCP)

Let Claude, Cursor, and other MCP-capable assistants work with your Fetchply agents by signing in or using an API key.

Fetchply is an MCP server. Connect an AI assistant once and it can list your agents, check how they perform, surface the questions they could not answer, read conversations, monitor your plan usage, and even talk to your agents directly, all by asking in plain language.

Nothing an assistant does through this connection can change or delete your data. The one non-reading tool is ask_agent, which sends a message to one of your agents: it uses a message credit and the conversation is saved to your Inbox, like any other conversation.

Two ways to connect

Sign in with your Fetchply account. For assistants that connect through a sign-in flow, like Claude custom connectors. Add the server URL, and the assistant sends you to the Fetchply login page to approve the connection. The assistant then sees all your agents with every tool available.
Use an API key. For assistants that let you set request headers, like Claude Code and Cursor. The assistant only sees the tools your key has permissions for, and you can limit the key to specific agents.

Either way, the server URL is the same: https://fetchply.com/api/v1/mcp

For the API key option, create the key on the API keys page in your dashboard and select the permissions you want the assistant to have. See creating an API key.

Claude (custom connectors)

In Claude, open Settings → Connectors and choose Add custom connector.
Enter https://fetchply.com/api/v1/mcp as the server URL and save. No key or header is needed.
Click Connect. A Fetchply sign-in window opens; log in with your Fetchply account (or approve directly if you are already signed in).
Once connected, ask Claude about your agents to confirm it works.

Claude Code

claude mcp add --transport http fetchply https://fetchply.com/api/v1/mcp \
  --header "Authorization: Bearer fp_live_YOUR_KEY"

Cursor

Add this to .cursor/mcp.json in your project (or the global Cursor settings):

{
  "mcpServers": {
    "fetchply": {
      "url": "https://fetchply.com/api/v1/mcp",
      "headers": { "Authorization": "Bearer fp_live_YOUR_KEY" }
    }
  }
}

Try it

Ask your assistant: "Which Fetchply agents do I have?" It should call the list_agents tool and show your agents.

Ask: "How is my agent doing this month?" The assistant combines the overview and analytics tools into a summary.

Ask: "What questions couldn't my agent answer this week?" and let it suggest what to train next.

Available tools

Tool	Permission	What it does
`list_agents`	`read:agents`	List your agents with ID, name, and status
`get_agent`	`read:agents`	Read one agent
`get_agent_overview`	`read:analytics`	Performance, demand, and attention items for a period
`get_agent_analytics`	`read:analytics`	Top questions, unanswered queries, satisfaction, locations
`get_unanswered_questions`	`read:analytics`	Questions the agent could not answer
`list_conversations`	`read:conversations`	Page through an agent's conversations
`get_conversation`	`read:conversations`	One conversation with its transcript
`get_usage`	`read:usage`	Message credits used and when they reset
`ask_agent`	`write:chat`	Send a message to an agent and get its answer (uses a message credit)

Both connection types give the assistant read access to your data, including conversation transcripts. Only connect assistants you trust. To cut off access, revoke the API key from the dashboard, or disconnect the connector in the assistant's settings.

When you connect by signing in, the assistant has every tool. When you connect with an API key, the assistant only sees the tools matching the key's permissions; leave Send messages unchecked on the key if the assistant should not talk to your agents or use message credits.

Troubleshooting

The assistant says no tools are available. The key has no permissions selected, or was revoked. Create a key with the permissions you need and update the connection.
A tool reports a missing permission. The key works but lacks that tool's permission. Create a key that includes it and update the header.
The connection fails with an API key. Check the URL is exactly https://fetchply.com/api/v1/mcp, the header name is Authorization, and the value is Bearer followed by a space and your full key.
The sign-in window closes but the connector shows as not connected. Remove the connector and add it again; if you were signed in to a different Fetchply account, log out of Fetchply first so you can sign in with the right one.
The connection stops working after a while. Sign-in based connections expire periodically and the assistant normally renews them on its own. If it does not, disconnect and reconnect the connector.
A tool says "not found or not accessible". The ID it used is wrong, the item was deleted, or the key is restricted to other agents. Asking the assistant to list agents or conversations first usually fixes it.
Requests suddenly fail after working. The connection may have hit its per-minute request allowance; the assistant can simply retry shortly.