Connect an MCP Client

The Copera MCP server is reachable at a single Streamable HTTP endpoint. Point your AI client at it, supply a bearer token, and the tool catalog appears automatically.

Endpoint

MCP endpoint	https://mcp.copera.ai/mcp
Transport	Streamable HTTP (POST)
Auth header	Authorization: Bearer cp_pat_… or cp_oat_…

Stateless transport

The server runs in stateless mode — there are no sessions to resume. Only POST /mcp is supported; GET and DELETE return 405. A health check is available at GET /health.

You will need a token before connecting. The simplest option is a Personal Access Token (cp_pat_…) created in your Copera workspace settings. See Authentication for PATs vs. OAuth and how scopes map to tools.

Connect a client

Create a token

Generate a Personal Access Token (cp_pat_…) in your Copera workspace and grant it the scopes your agent needs — for example access_boards and access_docs. Treat it like a password.

Add the server to your MCP client

Configure your client with the endpoint URL and the bearer token. Most clients accept either a remote-server config block or an mcp-remote bridge command.

Remote server (JSON)

{
  "mcpServers": {
    "copera": {
      "type": "http",
      "url": "https://mcp.copera.ai/mcp",
      "headers": {
        "Authorization": "Bearer cp_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

mcp-remote bridge

For clients that only support local stdio servers, bridge to the remote endpoint with mcp-remote:

{
  "mcpServers": {
    "copera": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.copera.ai/mcp",
        "--header",
        "Authorization: Bearer cp_pat_YOUR_TOKEN_HERE"
      ]
    }
  }
}

Reload and verify the tools appear

Restart or reload the MCP client. The copera server should connect and expose its tools (list_boards, search, search_docs, and so on). If the client supports tool discovery, you will see the full catalog described in the Tool reference.

Make your first call

Ask the model to call get_workspace_info — a read-only tool that confirms the token resolves to the right workspace. From there, list_boards → list_tables → list_rows walks the discovery flow.

OAuth connectors

Some clients (such as Claude with remote connectors) can connect via OAuth instead of a pasted token. When you add the server URL without a bearer, the client receives a 401 with a WWW-Authenticate challenge and starts the OAuth flow automatically, minting a cp_oat_… token. See Authentication.

Test with the MCP Inspector

The MCP Inspector is the fastest way to confirm connectivity and explore tools by hand before wiring up an agent.

Launch the Inspector

npx @modelcontextprotocol/inspector

Configure the connection

In the Inspector UI:

• Transport type: Streamable HTTP
• URL: https://mcp.copera.ai/mcp
• Authentication: add an Authorization header with the value Bearer cp_pat_YOUR_TOKEN_HERE

List and call tools

Connect, open the Tools tab, and you should see all 37 tools. Call get_workspace_info to verify the token, then try list_boards to confirm read access.

Keep tokens secret

Anyone holding your bearer token can act as you within its scopes. Do not commit tokens to source control or paste them into shared configs. Rotate a token immediately if it leaks.

Troubleshooting

Symptom	Likely cause
401 Unauthorized	Missing, malformed, or expired bearer token. Re-check the Authorization: Bearer … header.
403 Forbidden on a tool	The token lacks the scope that tool requires (e.g. access_docs for document tools). See Authentication.
405 Method Not Allowed	The client sent GET/DELETE to /mcp. The server is stateless — use POST.
Tools missing in the client	The server connected but the client filtered tools, or the token resolves to a workspace without that data. Verify with the Inspector.