Quickstart

There is nothing to install: the server is hosted at mcp.timepay.ai. Connect using OAuth when your client supports it, or use API-key headers.

URL:       https://mcp.timepay.ai/mcp
Header:    X-API-KEY: <your TIMEPAY_API_KEY>
Optional:  X-ORG-ID: <target organization ID>

Get your API key

Get it from the Console. Keep it secret: anyone with the key can read your account data and place calls.

Add the MCP server

Some clients, including Claude Code and Codex, detect OAuth support and start the authorization flow automatically. For clients that do not support OAuth, connect with the X-API-KEY header.

If your account belongs to multiple organizations, add the X-ORG-ID header with the ID of the organization you want to access. This header is only required when authenticating with X-API-KEY. However if you use OAuth, the flow will ask you to select the organization.

claude mcp add --transport http timepay https://mcp.timepay.ai/mcp

Claude Desktop only launches local (stdio) servers, so reaching this remote HTTP server needs the mcp-remote bridge. Add the following to claude_desktop_config.json:

{
  "mcpServers": {
    "timepay": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.timepay.ai/mcp",
        "--header", "X-API-KEY: <your TIMEPAY_API_KEY>"
      ]
    }
  }
}

Restart Claude Desktop after saving.

Add the following to .cursor/mcp.json:

{
  "mcpServers": {
    "timepay": {
      "url": "https://mcp.timepay.ai/mcp",
      "headers": { "X-API-KEY": "<your TIMEPAY_API_KEY>" }
    }
  }
}

Add the following to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "timepay": {
      "serverUrl": "https://mcp.timepay.ai/mcp",
      "headers": { "X-API-KEY": "<your TIMEPAY_API_KEY>" }
    }
  }
}

Connect using OAuth:

codex mcp add timepay --url https://mcp.timepay.ai/mcp

Complete the OAuth sign-in flow when prompted.

Add the following to settings.json. Zed does not support environment-variable interpolation in headers, so the key goes in directly:

{
  "context_servers": {
    "timepay": {
      "url": "https://mcp.timepay.ai/mcp",
      "headers": { "X-API-KEY": "<your TIMEPAY_API_KEY>" }
    }
  }
}

Point it at the URL and header above. If it only launches local (stdio) servers, bridge it with mcp-remote:

npx -y mcp-remote https://mcp.timepay.ai/mcp \
  --header "X-API-KEY: <your TIMEPAY_API_KEY>"

Verify the connection

Start a new conversation and ask:

List my timepay.ai agents

A real list in response means you are connected.

claude.ai (web and mobile) supports OAuth. Add https://mcp.timepay.ai/mcp as a custom connector and complete the OAuth sign-in flow.

Troubleshooting

Tools return an auth error

Check that the header reads exactly X-API-KEY: <your TIMEPAY_API_KEY>. If your account belongs to multiple organizations, also send X-ORG-ID: <target organization ID>. An invalid key returns a 403 from the underlying timepay.ai API.

Client cannot reach a remote HTTP server

Some clients, including Claude Desktop, only support locally run stdio servers. Use the mcp-remote bridge shown above.

Not sure the server is reachable

Test it directly with the MCP Inspector:

npx @modelcontextprotocol/inspector

Connect with transport Streamable HTTP, URL https://mcp.timepay.ai/mcp, and header X-API-KEY: <your TIMEPAY_API_KEY>. Add X-ORG-ID: <target organization ID> if your account belongs to multiple organizations.

Integrations

Extra

MCP Server

Quickstart

Quickstart

Troubleshooting

​Quickstart

​Troubleshooting

Quickstart

Troubleshooting