posit-dev / posit-dev/mcptools
Expose an embeddable JSON-RPC dispatch (mount into an existing httpuv app)
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 196
- Forks
- 21
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
mcp_server() owns its process: stdio blocks on a nanonext cv loop, HTTP starts its own httpuv::startServer() + service(Inf), and check_not_interactive() forbids embedding. Frameworks that already run httpuv (shiny, plumber2, ambiorix) can't mount an mcptools endpoint on their existing port/event loop.
Suggested shape:
dispatch <- mcp_dispatch(tools = ..., resources = ...)
# function(body, req = NULL) -> JSON-RPC response list | promise | NULL (notification)
with mcp_server() becoming a thin stdio/HTTP wrapper around it.
Part of #115.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading mcp_server(), especially its nanonext cv loop, httpuv::startServer(), service(Inf), and check_not_interactive() paths. Done means an embeddable mcp_dispatch(tools=..., resources=...) returns a JSON-RPC response list, promise, or NULL for notifications, while mcp_server() remains the stdio/HTTP wrapper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- api, backend, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100