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:
(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:
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.
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:
- Concepts: idempotency — why every paid tool needs a key
- Concepts: auth and scopes — API key vs. OAuth, what each can call
- Quickstart: REST — the same operation over HTTP