STACK
- getstack-run/stack
io.github.getstack-run/stack is a MCP server that provides a remote EU-hosted agent runtime control plane with roughly 80 OAuth-gated tools.
About
io.github.getstack-run/stack exposes STACK as a remote MCP endpoint—a runtime control plane aimed at AI agents that need broad operational tooling without self-hosting a mashup of micro-servers. developers experimenting with agent-native products can connect Claude Code or Cursor to the streamable HTTP URL, complete OAuth on first use, and inherit a large catalog of control tools rather than maintaining stdio binaries for each vendor. EU hosting may matter for data residency choices. This is infrastructure, not a single-domain API like Sentry or Seline: evaluate STACK when your agent workflow needs centralized runtime commands across services and you accept a hosted dependency. Pair it with your own app code and observability stack; it does not replace application-level testing or analytics MCPs.
- 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
STACK by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http stack https://mcp.getstack.run/mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
| Repository | getstack-run/stack ↗ |
What it does
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.
Who is it for?
Best when you're shipping agent-heavy workflows and want a hosted control plane with many tools and EU residency without building your own orchestration layer.
Skip if: Simple static sites, air-gapped local-only MCP setups, or teams that refuse remote OAuth-dependent control planes.
What you get
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
By the numbers
- Server version 1.0.0
- Remote URL https://mcp.getstack.run/mcp
- ~80 MCP tools (vendor stated)
Recommended MCP Servers
나라장터 낙찰정보나라장터 낙찰정보서비스 Open API를 위한 로컬 MCP 서버나라장터 사전규격나라장터 사전규격정보서비스 Open API를 위한 로컬 MCP 서버나라장터 입찰공고나라장터 입찰공고정보서비스(공공데이터포털 data.go.kr) Open API를 감싼 로컬 MCP 서버
Accelerators36 tools for AWS infrastructure, security compliance, AI workflows, and ACI governance.
ACMSApple Container MCP Server (ACMS) provides access to Apple's container CLI tool on macOS3
Acronis MCPThe first real CLI for the Acronis Cyber Protect Cloud platform - every tenant, agent, and usage15How it compares
Hosted multi-tool agent runtime MCP, not a single-service analytics or error-monitoring connector.
FAQ
Who is io.github.getstack-run/stack for?
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.