Servicenow Nodejs vs Swsd
A side-by-side look at the Servicenow Nodejs and Swsd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Servicenow Nodejs for support & service management work as a local process; choose Swsd 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 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.
Choose Swsd when
- You need dedicated capabilities in the Support & Service Management domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SWSD_TOKEN, SWSD_BASE_URL, SWSD_PROFILE.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Support & Service Management |
| Quality signal | 60/100 · Good | 45/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SERVICENOW_INSTANCEHAPPY_CONFIG_PATHHAPPY_MCP_BIND_HOSTHAPPY_MCP_API_TOKEN | SWSD_TOKENSWSD_BASE_URLSWSD_PROFILE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 56 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Servicenow Nodejs | View Swsd |
Tools & capabilities
Servicenow Nodejs tools 3
SERVICENOW_INSTANCESN-Set-Instanceinstance
Swsd 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.
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"
}
}
}
}
Swsd
{
"mcpServers": {
"swsd": {
"command": "npx",
"args": [
"-y",
"swsd-mcp"
],
"env": {
"SWSD_TOKEN": "YOUR_SWSD_TOKEN_HERE",
"SWSD_BASE_URL": "YOUR_SWSD_BASE_URL_HERE",
"SWSD_PROFILE": "YOUR_SWSD_PROFILE_HERE"
}
}
}
}
Frequently asked questions
Servicenow Nodejs is categorized under Support & Service Management and uses a local stdio subprocess. Swsd belongs to Support & Service Management and uses a local stdio subprocess. Pick Servicenow Nodejs for support & service management work and Swsd 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.
Servicenow Nodejs has no declared pricing — check the project's own site. Swsd 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 servicenow-nodejs and swsd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Servicenow Nodejs has a quality signal of 60/100 (Good) with 0 views, 0 installs and 56 GitHub stars. Swsd has 45/100 (Fair) with 0 views, 0 installs and 4 GitHub stars.