Arcade.dev
MCP runtime with authorization, permission, and production-grade tool execution.
Open source
Best when you have adopted MCP as a protocol and need a runtime layer that handles auth, permissions, and audit before agent tool calls hit production.
Selection advice
Choose Arcade.dev when MCP is your protocol but you need more than just server implementations—you need a production runtime with auth and permission boundaries.
Best for
- MCP runtime
- tool authorization
- production tool gateway
Not ideal for
- teams not using MCP
- projects where a single agent owns all tools
Core concepts
MCPauthorizationpermissionstool execution
Minimal implementation shape
Register MCP tools through Arcade.dev's runtime, define who can call what, and let agents invoke tools with audited authorization instead of raw MCP connections.