Ldm Inbox Check MCP vs Google Tag Manager MC… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Ldm Inbox Check MCP vs Google Tag Manager MCP Server
In-depth architectural comparison of the Ldm Inbox Check MCP and Google Tag Manager MCP Server 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
Ldm Inbox Check MCP
Marketing · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 59/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose Ldm Inbox Check MCP if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server if your workspace requires Marketing integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Ldm Inbox Check MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Supports 9 real email providers with IMAP-backed seed accounts, Reports per-provider folder placement: Inbox, Spam, Promotions, etc., Parses and reports SPF, DKIM, and DMARC authentication results.
Email inbox placement testing across Gmail, Outlook, Yahoo, Mail.ru and Yandex. Create a test, get seed addresses, see per-provider placement (Inbox/Spam/Promotions), SPF/DKIM/DMARC verdicts, and screenshots. Install: npx -y ldm-inbox-check-mcp.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
Category & Scope
Tools & Capabilities Breakdown
Ldm Inbox Check MCP Tools (6)
Supports 9 real email providers with IMAP-backed seed accounts
Reports per-provider folder placement: Inbox, Spam, Promotions, etc.
Parses and reports SPF, DKIM, and DMARC authentication results
Provides screenshots of inbox and spam views for select providers
Exposes 5 JSON-schema validated tools for test creation, status, listing, deletion, and API key info
Stable REST API integration without scraping, designed for AI agent use
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).
Ldm Inbox Check MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select Ldm Inbox Check MCP when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.
Popular comparisons with Google Tag Manager MCP Server
Primary tools included: Remote MCP server supporting Google OAuth authentication, Interface to Google Tag Manager API, Hosted server available at gtm-mcp.stape.ai.