Easily convert tool, agents and orchestrators from existing agent frameworks to MCP servers
Easily convert tool, agents and orchestrators from existing agent frameworks to MCP servers
automcp allows you to easily convert tools, agents and orchestrators from existing agent frameworks into MCP servers, that can then be accessed by standardized interfaces via clients like Cursor and Claude Desktop.
@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: OPENAI_API_KEY, SERPER_API_KEY. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"automcp": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"OPENAI_API_KEY": "your-value",
"SERPER_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OPENAI_API_KEY | Credential the server authenticates with. | Yes |
| SERPER_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.