STACK
Give agents a hosted EU control plane with a large MCP tool surface for runtime orchestration instead of wiring dozens of one-off integrations yourself.
Overview
io.github.getstack-run/stack is a MCP server for the Build phase that provides a remote EU-hosted agent runtime control plane with roughly 80 OAuth-gated tools.
What is this MCP server?
- Remote streamable-http MCP at https://mcp.getstack.run/mcp
- Approximately 80 MCP tools for agent runtime control
- OAuth authentication on first call (no manual token paste in server.json)
- EU-hosted STACK platform from getstack.run
- Server version 1.0.0
- Remote URL https://mcp.getstack.run/mcp
- ~80 MCP tools (vendor stated)
What problem does it solve?
Agents that need to act on cloud runtimes force you to stitch many small MCP servers and secrets together with no unified control surface.
Who is it for?
Indie builders shipping agent-heavy workflows who want a hosted control plane with many tools and EU residency without building their own orchestration layer.
Skip if: Simple static sites, air-gapped local-only MCP setups, or teams that refuse remote OAuth-dependent control planes.
What do I get? / Deliverables
You point your agent at STACK’s remote MCP URL, authenticate once via OAuth, and access a broad tool set for runtime orchestration from one integration.
- OAuth-connected access to ~80 STACK runtime MCP tools
- Single remote integration replacing multiple agent infra MCPs
- EU-hosted orchestration surface for agent workflows
Recommended MCP Servers
Journey fit
STACK lands on Build/agent-tooling as the primary shelf where you provision agent runtime capabilities; it also supports Operate when agents manage live workloads. A ~80-tool remote MCP control plane is agent infrastructure—how your assistant acts on cloud resources—not a single app feature integration.
How it compares
Hosted multi-tool agent runtime MCP, not a single-service analytics or error-monitoring connector.
Common Questions / FAQ
Who is io.github.getstack-run/stack for?
Solo developers and small teams building agent-driven products who need a consolidated remote MCP control plane instead of many separate stdio servers.
When should I use io.github.getstack-run/stack?
Use it during build and operate when your agent must execute runtime operations across STACK-managed infrastructure and you are fine with OAuth to a EU-hosted endpoint.
How do I add io.github.getstack-run/stack to my agent?
Register the remote MCP URL https://mcp.getstack.run/mcp with streamable-http transport in Claude Code or Cursor, complete OAuth on first call, then use STACK tools from your agent session.