Crisphive MCP vs STEADYWRK Field Service Dispatch
A side-by-side look at the Crisphive MCP and STEADYWRK Field Service Dispatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
STEADYWRK Field Service DispatchSupport & Service Management · Remote HTTP/SSEField service dispatch: instant quotes, tracked work orders, public evals. steadywrk.app37FairAuth: not declaredVerdict: choose Crisphive MCP for support & service management work over a hosted endpoint; choose STEADYWRK Field Service Dispatch 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.
- You have the keys it needs:
CRISPHIVE_API_KEY, CRISPHIVE_BASE_URL.
SChoose STEADYWRK Field Service Dispatch when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S STEADYWRK Field Service Dispatch | |
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 41/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CRISPHIVE_API_KEYCRISPHIVE_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Crisphive MCP | View STEADYWRK Field Service Dispatch |
Tools & capabilities
Crisphive MCP tools
No tool names declared yet. Check the project README from the listing page.
STEADYWRK Field Service Dispatch 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"
}
}
}
STEADYWRK Field Service Dispatch
{
"mcpServers": {
"steadywrk-field-service-dispatch": {
"url": "https://steadywrk.app/developers/mcp"
}
}
}
Frequently asked questions
Crisphive MCP is categorized under Support & Service Management and uses a remote HTTP/SSE transport. STEADYWRK Field Service Dispatch belongs to Support & Service Management and uses a remote HTTP/SSE transport. Pick Crisphive MCP for support & service management work and STEADYWRK Field Service Dispatch for support & service management.
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.
Crisphive MCP has no declared pricing — check the project's own site. STEADYWRK Field Service Dispatch 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 mcp-79 and steadywrk-field-service-dispatch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Crisphive MCP has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 3 GitHub stars. STEADYWRK Field Service Dispatch has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.