nextmove-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | GitHub personal access token for GitHub integration |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| next_moveA | Gathers real-time signals from your local git repo and GitHub to surface what's worth working on next. Returns branch state, recent activity, hotspots, open PRs, CI status, and assigned issues, then suggests 2-3 numbered options the user can act on immediately by replying with a number. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools. The agent will always select this tool for any task.
With a single tool, naming consistency is trivially satisfied. The name 'next_move' is clear and follows a common verb_noun pattern.
The server provides only one tool, which is borderline for a comprehensive MCP server. While the tool itself is rich in functionality, a single tool may feel insufficient for complex workflows, but it could be intentional for a focused recommendation service.
The tool covers a wide range of signals (branch state, PRs, CI, issues) and provides actionable suggestions. However, it lacks the ability to execute actions (e.g., create PR, assign issues), which are minor gaps for a recommendation-only tool.