posit-dev / posit-dev/mcptools
Consider non-tool elements with `mcp_tools()`
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 196
- Forks
- 21
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
Follow-up to #108.
On the server-side, mcp_server() gives us a broader entry point to support other content types, like prompts / instructions. We could just add an argument if we wanted to support those.
On the client-side, the mcp_tools() interface might paint us into a corner. The function is named mcp_tools() and is documented as returning a list that can be provided directly to ellmer::Chat$register_tools(). It's possible that the use cases of e.g. Notion / Atlassian / Databricks MCP servers we're imagining might end up needing to interface with the prompts / instructions fields. Probably worth waiting to give a go at that until we really have a need, though—it might be the case that really everything substantive lives in tools.
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 reviewing issue #108 and the mcp_server() and mcp_tools() entry points, including how mcp_tools() feeds ellmer::Chat$register_tools(). Determine whether prompts or instructions require a broader client interface, then document the chosen scope and acceptance criteria before attempting an implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100