Authentication errors (401)
Authentication failures return HTTP401 with a problem body, before any tool runs. Every 401 also carries a WWW-Authenticate header with resource_metadata="https://app.usequotable.com/.well-known/oauth-protected-resource/api/mcp", which is how clients that sign in know where to go:
detail tells you which case you hit.
Unknown API key.
Unknown API key.
This API key was revoked.
This API key was revoked.
This API key has expired.
This API key has expired.
The API key creator no longer has the required access.
The API key creator no longer has the required access.
Unknown access token. / The access token expired. / This access was revoked. / The access token was not issued for this server.
Unknown access token. / The access token expired. / This access was revoked. / The access token was not issued for this server.
The person who approved this connection no longer has the required access.
The person who approved this connection no longer has the required access.
OAuth sign-in
The client asks you to sign in
The client asks you to sign in
Only the owner or an integration admin of … can connect apps.
Only the owner or an integration admin of … can connect apps.
This request expired / This sign-in request expired or was already used.
This request expired / This sign-in request expired or was already used.
Unsupported sign-in method / Secure sign-in required / Wrong server
Unsupported sign-in method / Secure sign-in required / Wrong server
https://app.usequotable.com/api/mcp. Check the server URL in the app, update the app, or connect with an API key.Your workspace changed since this page loaded.
Your workspace changed since this page loaded.
Unverified app, or a warning that the app uses a well-known name
Unverified app, or a warning that the app uses a well-known name
Untrusted return address / Unknown app / Incomplete request
Untrusted return address / Unknown app / Incomplete request
https or localhost address can’t sign in; use an API key with them.For your security, sign in again before doing this.
For your security, sign in again before doing this.
The client keeps asking you to sign in again
The client keeps asking you to sign in again
Sign-in works but tools return insufficient_scope or not_found
Sign-in works but tools return insufficient_scope or not_found
Tool errors
These come back as a tool result with"isError": true. The connection is fine; the call couldn’t be answered.
insufficient_scope: This tool requires the … scope, which the key was not granted.
insufficient_scope: This tool requires the … scope, which the key was not granted.
not_found: No such brand in this workspace, or the key's project allowlist does not include it.
not_found: No such brand in this workspace, or the key's project allowlist does not include it.
project_id isn’t a brand this key can read. Either the id is wrong (ask your assistant to call list_projects first), or the key is limited to other brands. A key’s or connection’s brands can’t be changed: create a new key, or sign in again, with the brand you need.invalid_cursor: The cursor is not one this server issued; start from the first page.
invalid_cursor: The cursor is not one this server issued; start from the first page.
cursor was edited, truncated or taken from a different tool. Call the tool again without cursor and follow next_cursor from there.invalid_parameter: …
invalid_parameter: …
get_visibility range where from is after to, or one that spans more than 366 days. The message says which.MCP error -32602: Input validation error: Invalid arguments for tool …
MCP error -32602: Input validation error: Invalid arguments for tool …
project_id that isn’t a UUID, a limit above 100, or a date not in YYYY-MM-DD form. The message lists each field. Most assistants correct this on their own on the next try.forbidden: … (from run_agent)
forbidden: … (from run_agent)
rate_limited: Too many runs started with this credential. …
rate_limited: Too many runs started with this credential. …
run_agent was called many times in a short time. Wait the number of minutes in the message, and check that your assistant isn’t starting the same run in a loop. Pass an idempotency_key so a retried call doesn’t start a second run.conflict: …
conflict: …
idempotency_key was sent again with different inputs. Use a new key for a new run.internal: Something failed on our side. Request id ….
internal: Something failed on our side. Request id ….
HTTP errors
Mcp-Session-Id, and it doesn’t need one back. If your client reports a missing session, it’s expecting a stateful server; any client that follows the Streamable HTTP specification works without one.Results look wrong or empty
get_visibility returns an empty data array
get_visibility returns an empty data array
paused: true in list_projects), or the dates are in the future. Widen the range or check the brand in Quotable.search_demand returns no terms
search_demand returns no terms
location_code and language match the brand’s location exactly; language is a name such as English.Only some of my data comes back
Only some of my data comes back
limit (up to 100) or follows next_cursor.I can't see a brand
I can't see a brand
list_projects to see what it can read.The shopping tools return not_found for a brand I can read
The shopping tools return not_found for a brand I can read
get_shopping_overview and get_shopping_product need a plan that includes Shopping. Without it they answer not_found, like a brand outside the key’s reach.list_articles doesn't show documents from Quotable Agent
list_articles doesn't show documents from Quotable Agent
list_articles doesn’t read.The assistant doesn't use Quotable
The assistant doesn't use Quotable
Still stuck?
Test the key outside your client with cURL. If this works, the problem is in the client’s configuration:200 with a list of tools means the key and network are fine. See Other clients for more raw requests.