Query MCP
Ask questions about your data in Enterspeed using the MCP server for the Query API.
Management MCP
Inspect and configure your tenant — schemas, environments, sources, domains, and clients.
Documentation MCP
Search and retrieve documentation content or report back issues or suggestions.
Which one do you need?
Query MCP and Management MCP are complementary — many people connect both, so an agent can read a schema, change it, and then query the result.
How authentication works
Both tenant-facing servers are passthrough proxies that hold no credentials of their own. Every authorisation decision is made by the underlying Enterspeed API, never by the MCP server. They differ in how you identify yourself to them:
Signing in means the client sends you to Enterspeed in a browser window and keeps the resulting token. Clients that take a server URL and nothing else — claude.ai in the browser, Claude Desktop’s Connectors screen — work this way, because they have no field for a custom header.
A key remains the tighter boundary on Query MCP: one scoped to a single environment and index prefix gives an agent exactly that much and no more. On Management MCP, you narrow a signed-in connection with parameters on the server URL instead — for example
?readOnly=true — see Limiting a connection.
Transport
Both tenant-facing servers speak MCP Streamable HTTP on the root URL, and nothing else. Choose the HTTP or Streamable HTTP transport in your client. The older SSE transport does not work: a client set to SSE fails on its first request with an HTTP 400 error. There is no/sse endpoint — always configure the root URL.