CovaSyn

Connecting to the MCP server

CovaSyn exposes 225 deterministic tools across 18 tool families as an MCP server. Any MCP-capable client (Claude, Cursor, VS Code and others) connects via streamable HTTP.

Endpoint

https://mcp.covasyn.com/mcp

Transport: streamable HTTP, MCP protocol version 2025-06-18. Server-sent events are supported.

Authentication

Requests are authenticated with an API key, sent either as an X-CovaSyn-Key header or as Authorization: Bearer. See API keys and authentication for how to get one.

The server also speaks OAuth 2.1 with PKCE and dynamic client registration. Clients implementing the MCP OAuth flow connect without manual key entry. Discovery documents:

https://mcp.covasyn.com/.well-known/oauth-protected-resource
https://mcp.covasyn.com/.well-known/oauth-authorization-server

Client configuration

Claude Code:

claude mcp add --transport http covasyn https://mcp.covasyn.com/mcp \
  --header "X-CovaSyn-Key: <ihr-key>"

Claude Desktop, Cursor and VS Code (mcp.json):

{
  "mcpServers": {
    "covasyn": {
      "type": "http",
      "url": "https://mcp.covasyn.com/mcp",
      "headers": { "X-CovaSyn-Key": "<your-key>" }
    }
  }
}

Allowances

Your weekly allowance depends on the package we work out together in the intro call.

MCP server documentation | CovaSyn