chrisbanes / chrisbanes/ensemble
Implement github_graphql MCP tool for agent sessions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 0
- Avg merge
- 23h 12m
- Merged PRs (30d)
- 84
Description
Problem
SPEC Section 10.5 defines an optional MCP server tool that exposes raw GitHub GraphQL query/mutation access to the ACP agent session, using Ensemble's configured tracker auth. This would be exposed via the mcpServers parameter of session/new.
Currently, the session/new call in agent/acpx_client.rs passes mcpServers: {} (empty). There is no MCP server implementation and no code to forward GraphQL queries to GitHub.
Proposed approach
- Implement a lightweight MCP server that exposes
github_graphqlquery/mutation tools - Use the tracker's configured auth (GitHub token) for API calls
- Pass the MCP server config in the
mcpServersfield when creating ACP sessions - Gate behind opt-in config flag since this is a recommended extension (Section 18.2)
Contributor guide
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 with agent/acpx_client.rs, where session/new currently sends an empty mcpServers object, and read SPEC Section 10.5. Trace how configured tracker authentication is represented, then define the opt-in MCP server configuration and github_graphql query/mutation access. Done means an enabled session forwards the configured GitHub auth and exposes the tool, while the default remains disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- api, backend, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100