Codemcp vs NexusToken
A side-by-side look at the Codemcp and NexusToken MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codemcp for coding agents work as a local process; choose NexusToken for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codemcp when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose NexusToken when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
NEXUS_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 44/100 · Fair | 35/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | NEXUS_BASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,605 | 1 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Codemcp | View NexusToken |
Tools & capabilities
Codemcp tools
No tool names declared yet. Check the project README from the listing page.
NexusToken tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codemcp
{
"mcpServers": {
"ezyang-codemcp": {
"command": "uvx",
"args": [
"--from",
"git+https://github.com/ezyang/codemcp@prod",
"codemcp"
]
}
}
}
NexusToken
{
"mcpServers": {
"nexustoken": {
"command": "uvx",
"args": [
"nexustoken-sdk"
],
"env": {
"NEXUS_BASE_URL": "YOUR_NEXUS_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Codemcp is categorized under Coding Agents and uses a local stdio subprocess. NexusToken belongs to Coding Agents and uses a local stdio subprocess. Pick Codemcp for coding agents work and NexusToken for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codemcp is listed as free. Auth: no auth required. NexusToken has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ezyang-codemcp and nexustoken as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codemcp has a quality signal of 44/100 (Fair) with 6 views, 0 installs and 1,605 GitHub stars. NexusToken has 35/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.