> ## Documentation Index
> Fetch the complete documentation index at: https://wiredesk.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP server

> Give Claude, ChatGPT, Cursor or your own agent access to a Wiredesk workspace: its knowledge, conversations, contacts and leads, over the Model Context Protocol.

The MCP server lets an AI assistant use your workspace: answer from your agents' knowledge, look through conversations, find leads, and add contacts or knowledge. It offers the [REST API](https://wiredesk.ai/docs/developers/api.md)'s operations as tools.

```
https://wiredesk.ai/api/mcp
```

It uses the streamable HTTP transport and authenticates with an [API key](https://wiredesk.ai/docs/api-reference/authentication.md) sent as a bearer token. Make a key for the assistant under **Developers → API keys**. A **Read only** key gives the assistant only the read tools, which suits an assistant that should look but not change anything.

## Connect a client

### Claude Code

```bash theme={null}
claude mcp add --transport http wiredesk https://wiredesk.ai/api/mcp \
  --header "Authorization: Bearer wd_…"
```

### Cursor

In `.cursor/mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "wiredesk": {
      "url": "https://wiredesk.ai/api/mcp",
      "headers": { "Authorization": "Bearer wd_…" }
    }
  }
}
```

### Other clients

Any client that supports remote MCP servers over streamable HTTP with a custom `Authorization` header can connect. Clients that only connect with OAuth, such as custom connectors in the Claude and ChatGPT apps, cannot connect yet.

## Tools

| Tool | What it does |
| - | - |
| `list_agents`, `get_agent` | The workspace's agents |
| `update_agent` | Change an agent's name, greeting or instructions |
| `search_knowledge` | The passages an agent's knowledge holds about a question, best first |
| `list_knowledge_sources` | What an agent has been taught |
| `add_knowledge_source` | Teach an agent pasted text or a website |
| `delete_knowledge_source` | Remove a knowledge source |
| `send_message` | Send a message to an agent and get its reply |
| `list_conversations`, `search_conversations`, `get_conversation` | Conversations, with their summaries |
| `list_messages` | A conversation's transcript |
| `list_contacts`, `get_contact` | Contacts |
| `create_contact`, `update_contact`, `delete_contact` | Change contacts |
| `list_leads` | Leads the agents captured |
| `get_onboarding`, `claim_onboarding`, `delete_onboarding` | An [agent-first onboarding](https://wiredesk.ai/docs/developers/agent-onboarding.md): its setup checklist, the claim link, and deleting the trial |

Read tools are marked read-only and the three delete tools are marked destructive, so clients that ask before running a tool know which ones change things. A tool's result is the same JSON the REST API returns. A failure comes back as a tool error the assistant can read, such as `not_found: no agent with that id`.

Rate limits are the API's: 120 requests a minute per key.

Every response has an `x-request-id` header. Each call the assistant makes shows under **Developers → Logs**, named by its tool, with the arguments it sent. See [Request logs](https://wiredesk.ai/docs/developers/logs.md).

## Example prompts

* "Using Wiredesk, what does our support agent say about refunds?"
* "Find this week's Wiredesk conversations about delivery delays and summarise what customers asked."
* "List the leads Wiredesk captured yesterday as a table."

Starting an onboarding is not a tool: it is how a caller with no key gets one, so it is a REST call. See [Agent-first onboarding](https://wiredesk.ai/docs/developers/agent-onboarding.md). The key it returns works here.

## Related

* [Agent-first onboarding](https://wiredesk.ai/docs/developers/agent-onboarding.md)
* [REST API](https://wiredesk.ai/docs/developers/api.md)
* [Webhooks](https://wiredesk.ai/docs/developers/webhooks.md)
* [Request logs](https://wiredesk.ai/docs/developers/logs.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.