-
Notifications
You must be signed in to change notification settings - Fork 151
Serve MCP from the runtime #7357
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
|
Any reason for using SSE vs Streamable HTTP? Streamable HTTP would allow multiple clients to connect, but I haven't had the same luck with SSE, maybe I'm doing something incorrectly. |
The |
|
Gotcha, do you think this will be available on rill cloud or just for rill developer? If on rill cloud would be curious if this MCP will support multiple clients (claude desktop from different users) simultaneously? |
Yeah this will also be availability in Rill Cloud (see the third example Claude config in the PR note). And yeah it will support concurrent users/clients! Each user will authenticate with their own access token (initially you'll have to create it manually with this new CLI command, but we also plan on adding support for the OAuth redirect flows later). |
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.
👍
* Serve MCP from the runtime * MCP instructions * Implement all endpoints * Support dynamic instances + observability middleware * Support SSE and anonymous users in the runtime proxy * Update e2e test for GitHub Analytics example project * Review comments * Review comment * Standards compliant JSON schema for metrics view query * Review prompts * More prompt tuning --------- Co-authored-by: Eric P Green <[email protected]>
|
Do you think the mcp will ever support the ability to generate a rill url the end user can go to as partial evidence of the answer? My concern is it will spit out some numbers but it's really hard to say whether that is right or wrong, being able to corroborate it with a rill dashboard helps check the answer is correct but also continue to answer in the rill ui for the human operator. |
Implements an MCP server in the Rill runtime, enabling MCP clients to connect directly to Rill without starting a separate process.
Features:
http://localhost:9009/mcp/ssehttps://api.rilldata.com/v1/organizations/{org}/projects/{proj}/runtime/mcp/sseExamples:
Claude config for connecting to Rill Developer (must have
rill startrunning in a terminal):{ "mcpServers": { "rill": { "command": "npx", "args": [ "mcp-remote", "http://localhost:9009/mcp/sse" ] } } }Claude config for connecting to a public Rill Cloud project:
{ "mcpServers": { "rill": { "command": "npx", "args": [ "mcp-remote", "https://api.rilldata.com/v1/organizations/demo/projects/rill-github-analytics/runtime/mcp/sse" ] } } }Claude config for connecting to a private Rill Cloud project (use
rill token issueto get a personal access token):{ "mcpServers": { "rill": { "command": "npx", "args": [ "mcp-remote", "https://api.rilldata.com/v1/organizations/demo/projects/rill-openrtb-prog-ads/runtime/mcp/sse", "--header", "Authorization:${AUTH_HEADER}" ], "env": { "AUTH_HEADER": "Bearer <Rill access token>" } } } }Future work:
api.rilldata.com/v1/mcp)Checklist: