What is the key difference between Salesforce Metadata MCP and Next Devtools MCP?

Salesforce Metadata MCP belongs to the Developer Tools category with local stdio execution, while Next Devtools MCP belongs to the Developer Tools category with local stdio execution.

How do I install Salesforce Metadata MCP or Next Devtools MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Salesforce Metadata MCP and Next Devtools MCP free or paid?

Salesforce Metadata MCP operates under a Free / Open Source model (No auth required). Next Devtools MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Salesforce Metadata MCP lists 80 tools with 2 views and 2 GitHub stars. Next Devtools MCP lists 4 tools with 7 views and 825 GitHub stars.

Can I use both Salesforce Metadata MCP and Next Devtools MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Salesforce Metadata MCP vs Next Devtools MCP

In-depth architectural comparison of the Salesforce Metadata MCP and Next Devtools MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Salesforce Metadata MCP

Developer Tools · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Next Devtools MCP

Developer Tools · Local stdio

Quality: 84/100 (Excellent) | Auth: No auth required

Verdict Summary: Choose Salesforce Metadata MCP if you need specialized Developer Tools tools running via a local process. Choose Next Devtools MCP if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Salesforce Metadata MCP when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: SF_INSTANCE_URL, SF_ACCESS_TOKEN.
Primary tools included: sf_create_custom_object, sf_create_custom_field, sf_create_formula_field.

Explore Salesforce Metadata MCP Details

Choose Next Devtools MCP when:

You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: nextjs_index, nextjs_call, nextjs_docs.

Feature & Specification Comparison

Specification	Salesforce Metadata MCP Developer Tools	Next Devtools MCP vercel VerifiedDeveloper Tools
Summary	The only Salesforce MCP with Agentforce, OmniStudio & DevOps Center tools — 228 total.	Official Next.js MCP server for coding agents. Provides runtime diagnostics, route inspection, dev server logs, docs search, and upgrade guides. Requires Next.js 16+ dev server for full runtime features.
Category & Scope

Tools & Capabilities Breakdown

Salesforce Metadata MCP Tools (80)

sf_create_custom_object

Create a custom object with all settings

sf_create_custom_field

Create a field on any object (all types)

sf_create_formula_field

Create formula fields with full formula language support

sf_add_picklist_values

Add values to existing picklist fields

sf_create_custom_metadata_type

Create a Custom Metadata Type (__mdt)

sf_create_custom_metadata_record

Create records for a Custom Metadata Type

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Salesforce Metadata MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "salesforce-metadata-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "salesforce-metadata-mcp"
      ],
      "env": {
        "SF_INSTANCE_URL": "YOUR_SF_INSTANCE_URL_HERE",
        "SF_ACCESS_TOKEN": "YOUR_SF_ACCESS_TOKEN_HERE"
      }
    }
  }
}

Next Devtools MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "vercel-next-devtools-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "next-devtools-mcp@latest"
      ]
    }
  }
}

Frequently Asked Questions

Salesforce Metadata MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Next Devtools MCP belongs to Developer Tools using local stdio subprocess. Select Salesforce Metadata MCP when you need capabilities focused on developer tools and Next Devtools MCP when you require tools for developer tools.

More alternatives to Salesforce Metadata MCP More alternatives to Next Devtools MCP Developer Tools category hub