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. You connect to both servers by signing in with your Enterspeed account. You give your client the server URL, and it sends you to Enterspeed in a browser window where you sign in. The client keeps the resulting token. The steps for each client are under Connecting a client for the Query MCP and Connecting a client for the Management MCP. The Query MCP also accepts a scoped environment client key in anx-api-key header. Use one for an agent that runs unattended, because it cannot complete a browser sign in. Use one too when you want the connection fixed to one environment and one index scope. The Management MCP takes no key. You narrow a connection to it 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.