Ext Ops Panel
Open dashboard
Comparison

servicenow-sdk vs mtdt — Salesforce DevOps

servicenow-sdk is a plugin bundle for AI coding tools published by ServiceNow. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). mtdt — Salesforce DevOps is an MCP server published by mtdt.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
Marketplaceservicenow-sdkmtdt — Salesforce DevOps
Claude Code: claude-plugins-community Listed
Version: 06adf37
Forks (GitHub): 33
Stars (GitHub): 134
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.2
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

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

servicenow-sdk vs mtdt — Salesforce DevOps
Factservicenow-sdkmtdt — Salesforce DevOps
Marketplaces that list it11
Stars (GitHub) (differs)134 (better)0 (worse)
Forks (GitHub) (differs)33 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.mtdt.io)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/servicenow/sdkgithub.com/mtdt-io/mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (28 h ago)

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-sdk

In its own words, on Claude Code: claude-plugins-community:

This plugin gives Claude the knowledge to help developers build, extend, and manage ServiceNow applications, workflows, and agents using the ServiceNow SDK. It simplifies common development tasks, reduces setup and configuration friction, and allows ServiceNow development to be performed programmatically as part of an integrated development toolchain.

mtdt — Salesforce DevOps

In its own words, on Official MCP Registry:

mtdt.io MCP: Salesforce DevOps platform connector (metadata deployments, backups and more)

How to run each

servicenow-sdk As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install servicenow-sdk@claude-community

mtdt — Salesforce DevOps As a remote MCP server

Claude Code
claude mcp add --transport http mtdt https://mcp.mtdt.io

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only mtdt — Salesforce DevOps 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

Neither one's marketplaces publish the settings it asks for.

What it can do: servicenow-sdk · What it can do: mtdt — Salesforce DevOps · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built