Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.summand.com/llms.txt

Use this file to discover all available pages before exploring further.

The Summand MCP server is hosted at https://mcp.summand.com/mcp and authenticated via OAuth. The issues below are the most common ones we see.

​
401 immediately after connecting

The discovery flow worked but the issued token didn’t make it back. Disconnect the integration in your client, then re-add it. Some clients cache stale registrations — fully removing and re-adding clears them.

​
401 after a period of working fine

Your token expired or was revoked. Re-authorize the integration in your client.

​
403 Forbidden on a specific dataset

The dataset isn’t owned by or shared with the authenticated user. Open the dataset in summand.com and confirm sharing.

​
A tool call hangs or times out

Large semantic components (especially ebm_graphs and umap_embedding) can be hundreds of KB. Pass params to get_semantic_data to scope down — for example { "feature": "price" } returns only that feature’s contribution.

​
WWW-Authenticate header on every request

This is normal for the first call — it’s how the client discovers the OAuth server. If your client gets stuck looping on it, the client likely doesn’t support RFC 9728 discovery and isn’t compatible with the Summand MCP server.

​
My client asks for an API key

The Summand MCP server uses OAuth, not API keys. If your client is prompting for one, you’ve likely entered an API base URL by mistake — the correct value is https://mcp.summand.com/mcp. Configure it as a remote/HTTP MCP server in your client.

​
Still stuck?

Contact us with:
  • Which client you’re using (claude.ai, ChatGPT, etc.)
  • The exact error or behaviour
  • A timestamp of when the issue happened, so we can correlate with server logs