In-depth architectural comparison of the Umami MCP and Salesforce Metadata 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
Umami MCP
Developer Tools · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Salesforce Metadata MCP
Developer Tools · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Umami MCP if you need specialized Developer Tools tools running via a local process. Choose Salesforce Metadata 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 Umami 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: UMAMI_URL, UMAMI_USERNAME, UMAMI_PASSWORD, UMAMI_MCP_MODE, UMAMI_MCP_ALLOW_DESTRUCTIVE, UMAMI_MCP_ENV_FILE, UMAMI_MCP_OAUTH.
Umami MCP is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Salesforce Metadata MCP belongs to Developer Tools using local stdio subprocess. Select Umami MCP when you need capabilities focused on developer tools and Salesforce Metadata MCP when you require tools for developer tools.