ServiceNow MCP Server vs Trengo MCP by usefulapi
ServiceNow MCP Server is an MCP server published by jschuller. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Trengo MCP by usefulapi is an MCP server published by usefulapi.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ServiceNow MCP Server |   Trengo MCP by usefulapi |
|---|---|---|
| Official MCP Registry | Listed Version: 0.9.3 Downloads/month (PyPI): 1 362 Downloads/week (PyPI): 486 Forks (GitHub): 10 Stars (GitHub): 27 Not marked · First seen |
Listed Version: 1.37.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.9.3 Downloads/month (PyPI): 1 362 Downloads/week (PyPI): 486 Forks (GitHub): 10 Stars (GitHub): 27 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ServiceNow MCP Server | Trengo MCP by usefulapi |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 27 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 10 (better) | 0 (worse) |
| Last release (differs) | 2026-10-29 (worse) | 2026-11-10 (better) |
| Where it runs (differs) | On your machine (mcp-server-servicenow) | Remote server (trengo.usefulapi.io/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 15, secrets among them: 3 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/jschuller/mcp-server-servicenow | github.com/m190/usefulapi-mcp |
| Changes in the last 7 days (differs) | 2 | 12 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 15 h ago, requires authentication |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ServiceNow MCP Server
ServiceNow MCP server: Table API, CMDB, schema, aggregates, update sets and four Agent Skills.
Trengo MCP by usefulapi
Work tickets and messages, look up contacts and teams, pull reports, and reply, assign or close.
How to run each
ServiceNow MCP Server As a local MCP server: PyPI package
claude mcp add --env "SERVICENOW_API_KEY=<YOUR_SERVICENOW_API_KEY>" --env "SERVICENOW_CLIENT_SECRET=<YOUR_SERVICENOW_CLIENT_SECRET>" --env "SERVICENOW_INSTANCE_URL=<YOUR_SERVICENOW_INSTANCE_URL>" --env "SERVICENOW_PASSWORD=<YOUR_SERVICENOW_PASSWORD>" --transport stdio mcp-server-servicenow -- uvx mcp-server-servicenowRequires: SERVICENOW_API_KEY (secret), SERVICENOW_CLIENT_SECRET (secret), SERVICENOW_INSTANCE_URL, SERVICENOW_PASSWORD (secret)
Trengo MCP by usefulapi As a remote MCP server
claude mcp add --transport http trengo https://trengo.usefulapi.io/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Trengo MCP by usefulapi has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Trengo MCP by usefulapi publish no settings it asks for, so we do not compare settings.
What it can do: ServiceNow MCP Server · What it can do: Trengo MCP by usefulapi · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.