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

# MCP Server

> Connect Claude, Cursor, Windsurf, or any MCP client to your timepay.ai account with the timepay.ai MCP server.

# MCP Server

Connect Claude, Cursor, Windsurf, or any MCP client to your timepay.ai account with the timepay.ai MCP server.

The timepay.ai MCP server connects your AI assistant directly to your timepay.ai account over the [Model Context Protocol](https://modelcontextprotocol.io). Once connected, you can list, inspect, and delete agents, pull call transcripts, run batch campaigns, manage dispositions and phone numbers, check your wallet balance, and place outbound calls from a chat window.

It is hosted at **mcp.timepay.ai**, There is nothing to install or run locally: point your client at the URL with your API key and you are connected.

## What you can do

> **Action on your account**
>
> Ask it to "list my agents", "delete agent X", "list campaigns", "list dispositions", or "create a disposition" without opening the dashboard.

> **Debug a call**
>
> "Get the last 5 calls for agent X and show me the transcript" lets the assistant chain the lookups for you.

> **Manage agents**
>
> "List my agents" or "delete agent X" lets you inspect and remove agents from your account.

> **Manage phone numbers**
>
> "Buy me a number" lets you manage telephony alongside your agents.

## Authentication

Use one of the following authentication methods to connect to `https://mcp.timepay.ai/mcp`:

* **API key:** Send your API key in the `X-API-KEY` header. Do not send it as a Bearer token.
* **Multiple organizations:** When using `X-API-KEY` and your account belongs to multiple organizations, also send the target organization ID in the `X-ORG-ID` header.
* **OAuth:** Use OAuth from clients that cannot send custom headers directly, such as the Claude.ai (UI). The client handles the sign-in and authorization flow.

## How it works

Your client authenticates with an API key header or OAuth before connecting to `https://mcp.timepay.ai/mcp`. The server validates the credentials, calls the matching [API](https://agents.docs.timepay.ai/api-reference/agents/campaigns/list-campaigns.md) endpoint, and returns trimmed JSON your assistant can reason about.

```
Your client (Claude, Cursor, Windsurf...)
        |
  | X-API-KEY: <TIMEPAY_API_KEY>
  | X-ORG-ID: <TARGET_ORG_ID> (when required)
  | or OAuth
        v
https://mcp.timepay.ai/mcp
        |
        v
https://api.agents.timepay.ai  (agents | campaigns | dispositions | phone numbers | logs | transcripts)
```

## Confirm before it acts

Some MCP tools make permanent changes or create real-world effects, such as updating or deleting a campaign, starting an outbound call, scheduling a campaign, or buying a phone number. MCP clients commonly ask you to confirm before invoking these tools. Review the requested action carefully before approving it.


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