Very cool. How does activemcp figure out what tools I have defined? I haven't read the code, does it do a dynamic class lookup based on the tool name like rails does for controllers?
What's the right way to start the server in an existing rails app? Do I just create the server and call start in an initializer or something?
No. Any file that runs MCP Server is fine anywhere. I am intending a workspace separate from the rails app. The MCP server should be run in a separate process from the rails app. At least until the streamable http transport is ready.
Very cool. How does activemcp figure out what tools I have defined? I haven't read the code, does it do a dynamic class lookup based on the tool name like rails does for controllers?
What's the right way to start the server in an existing rails app? Do I just create the server and call start in an initializer or something?
Executed when a class inheriting from ActiveMcp::Tool is registered with its class name as the tool name and "tools/call" is requested in /mcp.
Simply mount the engine in route.rb, define the tool and start it.
> start it.
right I'm wondering where is the right place to start it! In an initializer?
No. Any file that runs MCP Server is fine anywhere. I am intending a workspace separate from the rails app. The MCP server should be run in a separate process from the rails app. At least until the streamable http transport is ready.
https://github.com/modelcontextprotocol/specification/pull/2... https://spec.modelcontextprotocol.io/specification/2025-03-2...