automcp

automcp is a CLI tool that auto-detects your coding agent (Cursor or VS Code) and scans your project's dependencies to automatically generate MCP (Model Context Protocol) server entries for GitMCP. It resolves each dependency to its GitHub repository and constructs GitMCP URLs, then updates your local MCP configuration without duplicating existing entries. You can run it in your project directory to apply changes, or use --dry-run to preview what would be added. The tool can target a specific agent or config location with --agent and --config, and it supports including development dependencies with --include-dev. After running, your MCP config will contain new servers like <dependency> Docs with their corresponding https://gitmcp.io/owner/repo URLs, ready to be consumed by your coding agents.

Prerequisites:

• Node.js (LTS) and npm installed on your system
• Access to the project directory where you want to add MCP entries

Install options:

1. Run without installing globally (recommended):

# In your project directory
npx automcp

2. Install as a development dependency in your project (also valid):

# In your project directory
npm add -D automcp
npx automcp

3. Alternatively, install and run via package manager if you prefer a local install (optional):

npm install --save-dev automcp
node_modules/.bin/automcp

Prerequisites recap:

• Ensure you have write access to the project directory you’re updating
• Ensure your project contains a package.json with dependencies to analyze
• If behind a proxy or firewall, ensure npm can reach registry and GitHub for repository lookup

Tips and caveats:

• AutoMCP updates only local project configurations (e.g., .cursor/mcp.json or .vscode/mcp.json); it does not modify global agent configurations.
• If a dependency lacks a GitHub repository or a repository field, it will be skipped.
• Use --dry-run to safely preview changes before applying them.
• You can target a specific agent or config path with --agent and --config; these flags can be used independently or together.
• Duplicates are prevented by URL normalization; however, manually editing the config may still be necessary in edge cases.
• The generated MCP entries use the GitMCP URL format: https://gitmcp.io/owner/repo