GitChanger MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gitchanger_statusA | Show current Git identity, matching GitChanger profile, remote URLs, and active GitHub MCP token status for the repository or global environment. |
| gitchanger_listB | List all configured Git profiles in GitChanger with their details. |
| gitchanger_switchA | Switch active Git profile for the current repository or globally. Automatically configures git user.name/email, SSH host alias/keys, adds key to ssh-agent, and syncs GitHub MCP token to AI clients. |
| gitchanger_addC | Add a new Git profile to GitChanger. |
| gitchanger_deleteC | Delete a Git profile from GitChanger. |
| gitchanger_set_defaultC | Set a profile as the default GitChanger profile. |
| gitchanger_test_sshC | Test SSH connection for a Git profile. |
| gitchanger_scanB | Scan ~/.ssh directory, SSH config, and MCP client configurations for existing keys and hosts. |
| gitchanger_mcp_statusB | Show GitHub MCP token status across profiles and detected AI client configurations (Antigravity, Claude, Cursor, VS Code). |
| gitchanger_mcp_setB | Set GitHub MCP Personal Access Token for a profile or directly into MCP client configs. |
| gitchanger_mcp_getB | Retrieve configured GitHub MCP token for a profile or active MCP client configuration. |
| gitchanger_mcp_syncB | Sync a profile's GitHub token to all detected MCP client configuration files. |
| gitchanger_mcp_testB | Test and verify GitHub token validity, account username, and OAuth scopes against GitHub API. |
| gitchanger_mcp_removeC | Remove GitHub MCP token from a profile and/or MCP client configs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| GitChanger Profiles | List of all configured Git profiles in JSON format |
| GitChanger Status | Current repository and Git identity status |
TDQS
Scored across 14 tools
Most tools target clearly distinct operations (add/delete/switch/scan/test_ssh vs. MCP token set/get/remove/sync/test). The main potential confusion is gitchanger_status vs gitchanger_mcp_status and gitchanger_list, which all report state, but descriptions make the split (identity/remote vs. token status vs. profile inventory) reasonably clear.
All tools use a consistent gitchanger_ prefix with snake_case verb/noun suffixes, and the MCP subgroup cleanly nests as gitchanger_mcp_*. No mixed camelCase or inconsistent verb styles.
14 tools is well within a reasonable range and each maps to a concrete operation across two coherent sub-domains (profile lifecycle and MCP token lifecycle). No obvious filler tools.
Profile CRUD is largely covered (add, delete, list, switch, set_default, status) plus SSH testing/scanning and full MCP token management (set/get/remove/sync/status/test). The notable gap is an update/edit operation for an existing profile's fields (e.g., changing name/email/SSH key without deleting and re-adding).