Skip to content

Securing Arcade MCP Deployments #582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
evantahler merged 2 commits into from
Dec 2, 2025
Merged

Securing Arcade MCP Deployments #582

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a7b598b
Securing Arcade MCP Deployments
evantahler Dec 2, 2025
56949e9
grammar
evantahler Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions app/en/home/serve-tools/_meta.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
export default {
"arcade-deploy": "Arcade Deploy",
"securing-arcade-mcp": "Securing Arcade MCP",
};
15 changes: 15 additions & 0 deletions app/en/home/serve-tools/securing-arcade-mcp/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Securing Arcade MCP Deployments

You may have noticed that when you connected to the MCP serer you created with `arcade-mcp`, you could immediately call your tools from local MCP Clients and agents, like Claude and Cursor. This is because the `arcade-mcp` server is *not* secured by any mechanism by default. Most use-cases for MCP servers today are local development or local to a single machine, and we optimize for that use-case.

However, you can secure your MCP server by deploying it to Arcade (available today) or using OAuth (coming soon).

## Arcade Deploy
When you `arcade deploy` your MCP server, it will be secured behind the Arcade platform.

Under the hood, we disable the MCP routes provided by `arcade-mcp`, and use the Arcade Engine as a gateway for your MCP server, which has a number of additional features. Arcade will create a randomized secure secret for your MCP server (via the `ARCADE_WORKER_SECRET` environment variable) so that your server is protected from unauthorized access, as well as being isolated from direct access from outside of the Arcade platform. Servers managed by Arcade (servers that are `arcade deploy`ed) serve `/worker` endpoints that are protected by this secret. The worker endpoints are `worker/health`, `/worker/tools`, and `/worker/tools/invoke`. The health endpoint is not protected by this secret, but the listing tools and tool invocations are. You can explore this locally by setting the same environment variable in your locally.

Learn more about how to deploy your MCP server to Arcade [here](/home/serve-tools/arcade-deploy).

## OAuth (Coming soon)
Coming soon, you will be able to secure your MCP server's `/mcp` endpoints with a OAuth Authorization Server (AS) - either using Dynamic Client Registration (DCR) or Client ID Metadata Documents (CIMD). Learn more about how MCP integrates with OAuth [here](https://blog.modelcontextprotocol.io/posts/client_registration/).
Copy link
Member

@EricGustin EricGustin Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

DCR in phase 1, CIMD in phase 2 (when I add DevEx for Arcade Intermediate AS!)