Arcade MCP Server
Build custom MCP servers and tools using a Python decorator-based framework.
Data last scanned today · Reviewed today
Overview
Arcade MCP is a Python-based framework designed for creating custom Model Context Protocol servers and specialized tools. It provides a decorator-driven API that supports the full MCP specification, including resources, prompts, and tool lifecycle management. By using this framework, developers can create tools that integrate with internal APIs or custom OAuth providers. The framework is built to be vendor-neutral, supporting various LLMs and agent frameworks. It features a specialized system for authorized tool calling that manages OAuth and API keys externally. This ensures that sensitive authentication data is handled securely and is not exposed directly to the AI client or the LLM during execution.
Our verdict
This server carries a high risk profile with a security score of 48/100. The primary factor contributing to this status is that it is community-maintained rather than developed by an official vendor, and critical security components like OAuth support and read-only mode compliance have not yet been editorially reviewed. It is suitable for developers building custom tooling who are comfortable managing their own security integrations, but it should be approached with caution in environments requiring strict audit trails.
- Supports the complete Model Context Protocol specification
- Zero direct dependencies minimize supply-chain surface
- Includes built-in testing tools for tool-call accuracy
- Not maintained by an official vendor organization
- Security implementation details lack independent editorial review
Tools
| Tool | Description | Risk |
|---|---|---|
| greet | Greet a person by name. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf | ||||
| ChatGPT |
Frequently asked questions
›What are the system requirements for arcade-mcp?
You need Python 3.10 or higher and the uv package manager to install and run the framework.
›How does authorized tool calling protect my credentials?
When using Arcade Cloud, OAuth tokens and API keys are stored securely in an encrypted environment and injected into the tool call at runtime. Neither the MCP client nor the LLM ever receive or see the actual secret values.
›Which authentication providers are supported out-of-the-box?
The framework includes 22 helper classes for popular services, including GitHub, Slack, Google, Notion, Linear, and Figma. You can also use a generic OAuth2 class for other providers.
›Can I run arcade-mcp servers without using Arcade Cloud?
Yes, standalone operation is supported. You can run servers locally over stdio or HTTP and manually supply access tokens for authenticated tools or implement Resource Server Auth for HTTP endpoints.
›How can I test the accuracy of my tool calls?
The framework includes an 'arcade evals' command specifically designed for testing tool-call accuracy against real LLMs.
Badge
Maintain this server? Add the live badge to your README.