Meridian MCP

Let your AI agent look up Meridian’s managed SEO and technical B2B content services.

Endpoint https://mcp.seekmeridian.com/mcp

Connect

Add this endpoint as a remote server URL in an MCP-compatible client.

Transport: Stateless Streamable HTTP.
Access: Anonymous and read-only. No API key or account required.
Browser check: Opening the endpoint in a browser returns 405. Connect through an MCP client.

Tool reference

The server exposes one tool, get_meridian_services. Call it with {} for the approved catalogue, or filter by service or question.

service: Optional string matched to an approved service_id, such as managed-technical-b2b-seo. Maximum 200 characters.
question: Optional string matched to approved FAQ text or a faq_id, such as who-is-meridian-for. Case and punctuation are ignored. Maximum 200 characters.

MCP tools/call example

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_meridian_services",
    "arguments": {}
  }
}

Results include approved services, fit information, FAQs, and contact details. An unmatched lookup returns answer_status: unknown_or_unapproved with the official contact route. Inputs are exact lookups, not semantic free-form search.

Limits and support

Limit: 60 MCP requests per minute per IP, with a burst of 20. Excess requests return 429 and Retry-After: 60.
Request bodies are limited to 64 KiB.
The public catalogue does not generate articles, place orders, publish content, or take payment.

Technical reference Contact Meridian