MCP server
Connect an MCP-capable client to AgentStack over Streamable HTTP.
AgentStack exposes a Streamable HTTP MCP endpoint at https://www.agentstack.build/api/mcp. It uses OAuth bearer authorization and does not rely on server-sent events. A missing, invalid, expired, or disabled-client token produces a JSON-RPC 401 response with a WWW-Authenticate resource-metadata challenge, so clients should complete the advertised authorization flow rather than substituting a REST API key.
The dashboard's MCP Server screen is the canonical place to copy a client configuration. It also shows authorized clients and recent MCP calls. The dashboard route under Dashboard is a re-export of the same MCP Server experience, so both routes share this guide. There is no server-side revoke button: remove or reconfigure the client locally and reconnect or re-authorize when credentials or requested access change.
Use MCP for an interactive developer client that needs delegated access to AgentStack. Use REST API keys for unattended services. The next guides cover scopes, tools, and client-specific setup patterns.