-
Notifications
You must be signed in to change notification settings - Fork 69
arcade deploy
for MCP Servers
#618
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.
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
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm reviewing with an eye to DX, and I think there are some minor things we can do to make this a really tight experience.
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice.
Blocked by #614 (and the reason for failing tests)
PR Description
arcade deploy
will deploy your local MCP server to Arcade.arcade deploy
should be executed at the root of your MCP Server package. Before deploying, the command runs your server locally to ensure your project is setup correctly and the server runs properly.arcade deploy
assumes your entrypoint file will executeMCPApp.run
when the file is invoked directly. This means you must either have anif __name__ == "__main__" block that contains
MCPApp.run, or
MCPApp.run` should be top-level code (unindented living directly in the body of the file).