MCP server · Dotdigital

dotdigital-api

Dotdigital hosts a remote MCP server for the Marketing Developer Hub. It is a documentation-and-specification discovery server, not a data-plane server: the seven tools read the published OpenAPI descriptions and the docs corpus so a coding agent can find the right endpoint and write the call. Actual API calls are still made over REST with Basic auth API-user credentials. tools/list answered anonymously on probe (HTTP 200, SSE transport).

Open endpoint → Dotdigital provider profile

One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.

Provider: Dotdigital Type: Hosted endpoint Transport: http Host: marketing.developer.dotdigital.com

Endpoint

https://marketing.developer.dotdigital.com/mcp

Hosted endpoint · transport http

Connect

This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):

# mcp client config (e.g. .mcp.json / mcp settings) { "mcpServers": { "dotdigital": { "url": "https://marketing.developer.dotdigital.com/mcp" } } }

For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:

# Add to claude_desktop_config.json { "mcpServers": { "dotdigital": { "command": "npx", "args": ["-y", "mcp-remote", "https://marketing.developer.dotdigital.com/mcp"] } } }

If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:

curl -i -X POST https://marketing.developer.dotdigital.com/mcp \ -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tools

list-endpoints — Lists all API paths and their HTTP methods with summaries, organized by path.
get-endpoint — Gets detailed information about a specific API endpoint, including security schemes and servers.
search-endpoints — Deep search through paths, operations and parameters to discover relevant API endpoints.
list-specs — Lists all available OpenAPI specs; the title selects a spec.
get-server-variables — Gets the server variables for each server within a specific OpenAPI spec.
search — Searches documentation, returning results with ID, title and URL.
fetch — Gets detailed content for documentation by ID returned from the search tool.

About MCP

The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.

Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.