Connect an MCP server

Drop a registry-hosted MCP server into Claude Desktop, Cursor, or VS Code. Two minutes start to finish.

1. Pick a server from the catalog

Browse /search?types=mcp-server. Open any entry that fits your stack. Note the id — you'll see it as <publisher>/<name>.

2. Copy the config snippet

Each MCP detail page has a Connect tab. Three sub-tabs cover the common clients:

// Claude Desktop · ~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" }
  }
}

// Cursor · ~/.cursor/mcp.json
{
  "mcpServers": {
    "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" }
  }
}

// VS Code · .vscode/settings.json
{
  "mcp.servers": {
    "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" }
  }
}

The URL is stable per skill_id — publishers can rotate their upstream and your config keeps working.

3. Restart your client

Claude Desktop, Cursor, and VS Code each load MCP config at startup; restart the app to pick up the new server.

How the proxy works

Every request is rate-limited per IP × per skill (60/min default).
Only verified and official tier publishers are proxied by default — unverified servers return 403 with a hint to install the publisher's URL directly.
Upstream URLs are SSRF-checked at submit time and at every request — we reject loopback, private, link-local, and metadata IPs.
A 60-second health probe surfaces a "healthy/unhealthy" badge on each server's detail page; unhealthy for ≥3 consecutive checks emails the publisher.

See /docs/mcp-proxy for the full security model.

Programmatic access

The SDK ships a one-shot helper that returns the same JSON snippet:

import { Skills } from '@amitte-ai/sdk';
const skills = new Skills({ registry: 'https://registry.amitte.com' });
const config = await skills.connectMcp('<publisher>/<name>', { client: 'claude-desktop' });
console.log(JSON.stringify(config, null, 2));

Or via the CLI:

npx @amitte-ai/cli connect <publisher>/<name> --client claude-desktop

2. Copy the config snippet

Each MCP detail page has a Connect tab. Three sub-tabs cover the common clients:

// Claude Desktop · ~/Library/Application Support/Claude/claude_desktop_config.json { "mcpServers": { "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" } } }

// Cursor · ~/.cursor/mcp.json { "mcpServers": { "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" } } }

// VS Code · .vscode/settings.json { "mcp.servers": { "<name>": { "url": "https://registry.amitte.com/mcp/<publisher>/<name>" } } }

The URL is stable per skill_id — publishers can rotate their upstream and your config keeps working.

How the proxy works

Every request is rate-limited per IP × per skill (60/min default).

Only verified and official tier publishers are proxied by default — unverified servers return 403 with a hint to install the publisher's URL directly.

Upstream URLs are SSRF-checked at submit time and at every request — we reject loopback, private, link-local, and metadata IPs.

A 60-second health probe surfaces a "healthy/unhealthy" badge on each server's detail page; unhealthy for ≥3 consecutive checks emails the publisher.

See /docs/mcp-proxy for the full security model.

Programmatic access

The SDK ships a one-shot helper that returns the same JSON snippet:

import { Skills } from '@amitte-ai/sdk'; const skills = new Skills({ registry: 'https://registry.amitte.com' }); const config = await skills.connectMcp('<publisher>/<name>', { client: 'claude-desktop' }); console.log(JSON.stringify(config, null, 2));

Or via the CLI:

npx @amitte-ai/cli connect <publisher>/<name> --client claude-desktop