- Home
- MCP servers
- Git-Steer
Git-Steer
- javascript
0
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"ry-ops-git-steer": {
"command": "npx",
"args": [
"git-steer"
],
"env": {
"GIT_STEER_APP_ID": "123456",
"GIT_STEER_PRIVATE_KEY": "-----BEGIN PRIVATE KEY-----..."
}
}
}
}You can run a self-hosted MCP server that gives you autonomous, natural-language control over your GitHub account. The server acts as the brain, while your computer provides the secure access point, keeping all state in a private repository and performing code changes through ephemeral cloud workers. This setup enables you to manage repos, branches, security, Actions, and more without cloning code locally.
How to use
Start by launching the MCP server through your preferred local runtime. The server accepts natural language intent and translates it into actions that are executed on GitHub. Typical workflows include scanning repositories for vulnerabilities, dispatching workflows to fix issues, managing branches and protections, and querying the status of dispatched actions.
How to install
Prerequisites: ensure you have a modern version of Node.js and npm installed on your machine.
- Install and initialize the MCP server for the first time.
# First-time setup
npx git-steer init
# Start the MCP server
npx git-steer
Additional notes
You can run the MCP server in standard mode using a simple local command, or you can operate from a locally checked-out version of the project. The common start command is shown below in the Quick Start examples.
Troubleshooting and tips
If you encounter offline behavior, the server operates in read-only mode using cached state and will queue write operations for the next online session. Ensure your GitHub App credentials are securely stored in your keychain and that your private state repository is accessible when online.
Examples of typical use
You can say or type prompts like: “List all my repos,” “Scan all my repos for security vulnerabilities,” or “Fix the critical vulnerabilities in cortex.” The server translates these prompts into actions such as listing repositories, performing vulnerability scans, dispatching protection workflows, or checking the status of dispatched workflows.
Available tools
repo_list
List all repositories accessible to the authenticated GitHub App.
repo_create
Create a new repository, optionally from a template.
repo_archive
Archive an existing repository to prevent further changes.
repo_delete
Permanently delete a repository (requires explicit confirmation).
repo_settings
Update repository settings through the MCP server controls.
branch_list
List branches with staleness information for maintenance.
branch_protect
Apply protection rules to branches to enforce policies.
branch_reap
Delete stale or merged branches according to criteria.
security_scan
Scan repositories for vulnerabilities and provide fix recommendations.
security_fix_pr
Dispatch a workflow to fix vulnerabilities by creating a PR.
security_alerts
List Dependabot and code-scanning alerts across managed repos.
security_dismiss
Dismiss an alert with a reason.
security_digest
Provide a summary of security posture across managed repositories.
actions_workflows
List GitHub Actions workflows in managed repos.
actions_trigger
Manually trigger a GitHub Actions workflow.
actions_secrets
Manage GitHub Actions secrets.
workflow_status
Check the status of dispatched workflows.
config_show
Display current MCP server configuration.
config_add_repo
Add a repository to the managed list.
config_remove_repo
Remove a repository from the managed list.
steer_status
Check health and rate limits of the MCP server.
steer_sync
Force the MCP server to save its state to GitHub.
steer_logs
View the audit log of actions and state changes.