Solved Docs

Quickstart: MCP (5 minutes)

The same call from an MCP client — Claude Code, Cursor and similar.

Goal: call the same operation as the REST quickstart, from an MCP-aware client (Claude Code, Cursor, or any client that lets you set a custom header).

1. Get a key. Same key as REST — one credential, both surfaces. See API keys.

2. Point your client at the server. Solved's MCP endpoint is Streamable HTTP, one URL per product:

{
  "mcpServers": {
    "solved-link": {
      "url": "https://api.link.solved.group/mcp",
      "headers": { "Authorization": "Bearer slv_live_e17Hk2Qp…9xZr4fT2aB" }
    }
  }
}

(Exact config keys depend on your client — this is the shape Claude Code and Cursor both accept today. Remote OAuth sign-in for hosted connectors — Claude.ai, ChatGPT — ships in wave 2; until then, API-key clients work immediately.)

3. Call a tool. Ask your agent to shorten a URL, or call link_create directly:

{ "destination_url": "https://example.com/spring", "slug": "spring-sale",
  "idempotency_key": "8f1c6e2a-9b7d-4e3f-9a21-9c2b7a0f5e41" }

Paid write tools always require idempotency_key for the same reason as the REST header — a retried tool call must not double-charge.

4. Read the result.

{
  "id": "lnk_01J9Z4A7R3V5W2XN4V6B0RTC5H",
  "short_url": "https://slv.link/spring-sale",
  "destination_url": "https://example.com/spring",
  "created_at": "2026-10-02T12:00:00Z",
  "credits_charged": 1,
  "credits_balance": 2499
}

Same fields as REST — structuredContent mirrors the JSON response, and a human-readable line is in content. On error you get isError: true with a stable error_code your agent can act on (not a protocol-level JSON-RPC error) — see Concepts: errors.

Check your balance any time without a paid call: every server also exposes solved_whoami and solved_get_credit_balance.

Where to next: