Hexis vs Trace MCP
A side-by-side look at the Hexis and Trace MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hexis for developer tools work as a local process; choose Trace MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hexis when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ADMIN_EMAIL, ADMIN_PASSWORD, JWT_SECRET, SECRETS_ENC_KEY.
Choose Trace MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 48/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | ADMIN_EMAILADMIN_PASSWORDJWT_SECRETSECRETS_ENC_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 116 | 193 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hexis | View Trace MCP |
Tools & capabilities
Hexis tools
No tool names declared yet. Check the project README from the listing page.
Trace MCP 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.
Hexis
{
"mcpServers": {
"hexis": {
"command": "npx",
"args": [
"-y",
"@bevel-software/hexis-mcp"
],
"env": {
"ADMIN_EMAIL": "YOUR_ADMIN_EMAIL_HERE",
"ADMIN_PASSWORD": "YOUR_ADMIN_PASSWORD_HERE",
"JWT_SECRET": "YOUR_JWT_SECRET_HERE",
"SECRETS_ENC_KEY": "YOUR_SECRETS_ENC_KEY_HERE"
}
}
}
}
Trace MCP
{
"mcpServers": {
"nikolai-vysotskyi-trace-mcp": {
"command": "npx",
"args": [
"-y",
"trace-mcp"
]
}
}
}
Frequently asked questions
Hexis is categorized under Developer Tools and uses a local stdio subprocess. Trace MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Hexis for developer tools work and Trace MCP for developer tools.
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.
Hexis is listed as free. Trace MCP is listed as free. Auth: no auth required. 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 hexis and nikolai-vysotskyi-trace-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hexis has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 116 GitHub stars. Trace MCP has 63/100 (Good) with 2 views, 0 installs and 193 GitHub stars.