Connect via MCP

MCP (Model Context Protocol) lets you use Kovrex agents directly inside your AI tools. No SDK. No code. Your subscribed agents appear as callable tools.

One-click setup (recommended)

The fastest path. Works with Claude.ai, Claude Desktop, and Cursor.

Find Kovrex in your tool's connector directory

Claude.ai / Claude Desktop: Settings → Connectors → Add → search “Kovrex”Cursor: Browse MCP Tools → search “Kovrex”

Authorize with your Kovrex account

You’ll be redirected to Kovrex to log in. Authorize the connection.

Use your agents

Your subscribed agents appear as tools. Ask Claude to use them directly in conversation.

That’s it. If you’re subscribed to the News Salience Filter, you can now say: “Use the news salience tool to check if this headline matters for NVDA.” Claude calls the agent, gets the structured response, and interprets the results for you.

Manual setup (API key)

If you prefer config files over OAuth, you can connect with an API key.

Get your API key

Create one at kovrex.ai/dashboard/api-keys. See API Keys for details.

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "kovrex": {
      "url": "https://gateway.kovrex.ai/mcp",
      "headers": {
        "X-API-Key": "kvx_live_your_key_here"
      }
    }
  }
}

Restart Claude Desktop. Kovrex tools appear in your tool list.

Cursor

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "kovrex": {
      "url": "https://gateway.kovrex.ai/mcp",
      "headers": {
        "X-API-Key": "kvx_live_your_key_here"
      }
    }
  }
}

Restart Cursor. Kovrex tools appear as available MCP tools.

Keep your API key out of version control. Use environment variables or a secrets manager for shared projects.

What you see after connecting

Your subscribed agents appear as tools with descriptive names:

Agent	MCP tool name
News Salience Filter	`analyze_news_salience`
URL Safety Check	`check_url_safety`

OAuth users see only agents they’re subscribed to. The tool list updates automatically when you add or remove subscriptions. API key users see all available agents. Each tool includes a description and input schema so Claude and Cursor know how to call it. You don’t need to configure anything per agent.

Sandbox vs production

MCP honors the same key types as the REST API:

Key type	Prefix	Behavior
Live	`kvx_live_`	Real calls, billed
Test	`kvx_test_`	Sandbox calls, free

Use test keys during development. Switch to live keys when you’re ready for production data. OAuth connections use your subscription’s key type (currently all live).

File operations

Two file tools are available to all authenticated users:

Tool	Description
`upload_file`	Upload files for agent processing (10MB max, 1hr TTL)
`get_file`	Retrieve uploaded files by ID

Use these when an agent needs to process a document, spreadsheet, or other file input.

Compress large files with gzip before uploading. The 10MB limit applies to the uploaded payload.

Transport protocols

The MCP endpoint supports three transports:

Transport	Endpoint	Best for
Streamable HTTP (recommended)	`POST /mcp`	Most clients. Best session persistence.
SSE (legacy)	`GET/POST /mcp/sse`	Older clients that require Server-Sent Events
Direct tool call	`POST /mcp/tools/call`	Simple one-off invocations

Most users don’t need to think about this. Claude Desktop and Cursor handle transport selection automatically.

Troubleshooting

Tools not showing up after connecting

OAuth: Make sure you have active agent subscriptions. No subscriptions = no tools.API key: Verify the key is valid and not expired. Check for typos in the config file.Both: Restart your client after connecting. Some tools require a fresh session to discover new MCP servers.

Getting 401 errors

Your token or API key may have expired. For OAuth, disconnect and reconnect. For API keys, check the key is active in your dashboard.

Agent calls timing out

Some agents take several seconds to respond, especially for complex queries. MCP connections have a default timeout. If you’re hitting timeouts consistently, check the agent’s typical latency on its prospectus page.

OAuth redirect not working

Make sure you’re using a supported client version. The OAuth flow requires Dynamic Client Registration support. Update Claude Desktop or Cursor to the latest version.

OAuth endpoints (reference)

For developers building custom MCP integrations:

Endpoint	Purpose
`POST /oauth/register`	Dynamic Client Registration
`GET /oauth/authorize`	Authorization
`POST /oauth/token`	Token exchange
`GET /mcp`	MCP manifest (discovery)
`POST /mcp`	JSON-RPC (Streamable HTTP)

Next steps

Browse Agents

Find agents to subscribe to

API Keys

Manage keys for manual setup

Calling Agents

Use agents via REST API instead

Rate Limits

Understand usage limits

Getting Started

Consumer Guide

Operator Guide

Examples

API Reference

Policies

Connect via MCP

One-click setup (recommended)

Manual setup (API key)

Get your API key

Claude Desktop

Cursor

What you see after connecting

Sandbox vs production

File operations

Transport protocols

Troubleshooting

OAuth endpoints (reference)

Next steps

Browse Agents

API Keys

Calling Agents

Rate Limits

​One-click setup (recommended)

​Manual setup (API key)

​Get your API key

​Claude Desktop

​Cursor

​What you see after connecting

​Sandbox vs production

​File operations

​Transport protocols

​Troubleshooting

​OAuth endpoints (reference)

​Next steps

Browse Agents

API Keys

Calling Agents

Rate Limits

One-click setup (recommended)

Manual setup (API key)

Get your API key

Claude Desktop

Cursor

What you see after connecting

Sandbox vs production

File operations

Transport protocols

Troubleshooting

OAuth endpoints (reference)

Next steps