Fieldproxy vs Servicenow Nodejs
A side-by-side look at the Fieldproxy and Servicenow Nodejs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Fieldproxy for support & service management work over a hosted endpoint; choose Servicenow Nodejs for support & service management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Servicenow Nodejs when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SERVICENOW_INSTANCE, HAPPY_CONFIG_PATH, HAPPY_MCP_BIND_HOST, HAPPY_MCP_API_TOKEN. - You want tools like
SERVICENOW_INSTANCE, SN-Set-Instance, instance.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 40/100 · Fair | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FIELDPROXY_MCP_KEY | SERVICENOW_INSTANCEHAPPY_CONFIG_PATHHAPPY_MCP_BIND_HOSTHAPPY_MCP_API_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 56 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Fieldproxy | View Servicenow Nodejs |
Tools & capabilities
Fieldproxy tools
No tool names declared yet. Check the project README from the listing page.
Servicenow Nodejs tools 3
SERVICENOW_INSTANCESN-Set-Instanceinstance
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.
Fieldproxy
{
"mcpServers": {
"fieldproxy": {
"url": "https://www.fieldproxy.ai/mcp"
}
}
}
Servicenow Nodejs
{
"mcpServers": {
"servicenow-nodejs": {
"command": "npx",
"args": [
"-y",
"happy-platform-mcp"
],
"env": {
"SERVICENOW_INSTANCE": "YOUR_SERVICENOW_INSTANCE_HERE",
"HAPPY_CONFIG_PATH": "YOUR_HAPPY_CONFIG_PATH_HERE",
"HAPPY_MCP_BIND_HOST": "YOUR_HAPPY_MCP_BIND_HOST_HERE",
"HAPPY_MCP_API_TOKEN": "YOUR_HAPPY_MCP_API_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Fieldproxy is categorized under Support & Service Management and uses a remote HTTP/SSE transport. Servicenow Nodejs belongs to Support & Service Management and uses a local stdio subprocess. Pick Fieldproxy for support & service management work and Servicenow Nodejs 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.
Fieldproxy has no declared pricing — check the project's own site. Servicenow Nodejs 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 fieldproxy and servicenow-nodejs as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fieldproxy has a quality signal of 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Servicenow Nodejs has 60/100 (Good) with 0 views, 0 installs and 56 GitHub stars.