- Remote servers over Streamable HTTP. Quotable doesn’t serve the older SSE transport.
- One way to authenticate: MCP OAuth sign-in, or custom request headers so it can send
Authorization: Bearer quotable_live_….
Sign in with OAuth
Clients that implement the MCP authorization specification need only the server URL,https://app.usequotable.com/api/mcp. On the first request the server answers 401 with a WWW-Authenticate header pointing at its metadata; the client registers itself, opens a Quotable approval page in your browser, and stores the tokens. See Authentication → For client developers for the endpoints.
The client’s sign-in must return to an https address or to localhost, 127.0.0.1 or [::1]. Clients that return to a custom app link (a non-web scheme) can’t use OAuth with Quotable; use an API key with them.
Send an API key
Most clients describe a remote server with a URL and a headers object, under a key such asmcpServers or servers:
url, serverUrl, httpUrl), and some need "type": "http". Check your client’s documentation, and read the key from an environment variable if the client supports it.
How the server behaves
Every POST counts toward the rate limit of 300 requests per minute per key or OAuth connection, including
initialize, notifications and tools/list. Successful responses carry X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset and an X-Request-Id to quote to support.
Call it with cURL
You can call any method directly. Set your key first:1
Initialize (optional)
Response
initialize to negotiate a protocol version. A script can skip straight to the next step.2
List the tools
title, description, JSON Schema inputSchema and annotations. run_agent is the one with readOnlyHint: false. See Tools.3
Call a tool
Response
content for clients that read text, and as an object in structuredContent.MCP-Protocol-Version is optional on requests after initialize. If you send it, use a version the server supports, such as 2025-06-18; an unsupported value gets 400.Errors
Errors arrive at two levels:- HTTP errors happen before any tool runs: a missing or invalid key or token (
401, with aWWW-Authenticateheader naming the sign-in metadata), the rate limit (429), a wrong method (405), a body that is too large (413), or a missingAcceptorContent-Typeheader (406,415). Authentication errors use the same problem format as the REST API. See Errors. - Tool errors come back as a normal JSON-RPC result with
"isError": trueand a message in the form<code>: <message>, for examplenot_found: …orinsufficient_scope: …. See Tools → Errors.
Next steps
Tools reference
Inputs and outputs for each tool.
Troubleshooting
Every error message and what to do.
REST API
The same data without MCP.