Crisphive MCP vs Fieldproxy
A side-by-side look at the Crisphive MCP and Fieldproxy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Crisphive MCP for support & service management work over a hosted endpoint; choose Fieldproxy for support & service management over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Crisphive MCP when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
CRISPHIVE_API_KEY, CRISPHIVE_BASE_URL.
Choose Fieldproxy when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
FIELDPROXY_MCP_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 43/100 · Fair | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CRISPHIVE_API_KEYCRISPHIVE_BASE_URL | FIELDPROXY_MCP_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Crisphive MCP | View Fieldproxy |
Tools & capabilities
Crisphive MCP tools
No tool names declared yet. Check the project README from the listing page.
Fieldproxy 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.
Crisphive MCP
{
"mcpServers": {
"mcp-79": {
"url": "https://api.crisphive.com/mcp"
}
}
}
Fieldproxy
{
"mcpServers": {
"fieldproxy": {
"url": "https://www.fieldproxy.ai/mcp"
}
}
}