MCP

Connect a remote macro-data MCP server in under a minute

Meridian exposes remote MCP access for teams that want live macro and market data inside agent clients without maintaining their own server wrapper.

Primary interface

Remote SSE MCP server plus compare and snapshot tools

Best first action

Add Meridian to your MCP client

Canonical URL

/mcp/macro-data-server

Example query

Ask a concrete question first

Each page is built around a real macro question so search visitors can immediately see how Meridian fits into an app or agent workflow.

Compare today's macro backdrop with 2008_crisis and explain the biggest differences.
This page is static by design. The snippets below are illustrative and do not fetch live data during build.

API example

Call the underlying API

Use the same product surface behind the demo and MCP integration when you need direct HTTP access.

curl -H "Authorization: Bearer mrd_your_key_here" \
  "https://api.meridianapi.io/v1/compare?compare_to=2008_crisis&indicators=UNRATE,CPIAUCSL,FEDFUNDS,T10Y2Y"

Response shape

What the MCP flow returns

The MCP client gets tool output that is ready to feed back into the model for reasoning, summarization, and follow-up questions.

A normalized tool payload instead of screen-scraped HTML.
Indicator-level context for inflation, labor, rates, and yield-curve interpretation.
Historical regime comparisons that an agent can summarize immediately.

MCP snippet

Connect the same workflow over MCP

Use placeholder credentials only on public pages, then swap in your own API key after signup.

Ask your MCP client: "Use Meridian to compare the current regime to 2008_crisis and tell me which indicators differ most."

{
  "mcpServers": {
    "meridian": {
      "url": "https://api.meridianapi.io/sse",
      "headers": {
        "Authorization": "Bearer mrd_your_key_here"
      }
    }
  }
}

Why teams use this

What this page helps you ship

These are the most common implementation reasons teams land on this route from search and move into a product workflow.

Remote MCP avoids shipping or hosting a custom macro-data adapter yourself.
The same Meridian data layer stays available over REST for product code and backend jobs.
Placeholder credentials keep setup snippets safe for public pages and docs.

FAQ

Questions search visitors usually ask next

Short answers keep these pages useful for humans while staying grounded in the product Meridian already exposes.

Which MCP clients fit this page?

Any client that supports remote SSE MCP servers can use the Meridian configuration snippet with your own API key.

Is the MCP server separate from the API?

It is the same Meridian data layer exposed through a different interface, so teams can mix MCP for agents and REST for applications.

What is the quickest verification step?

Paste the config, restart the client, and ask a macro comparison question that references inflation, unemployment, or the yield curve.

Try the demo, then move to a key-backed workflow

Start with Ask Meridian on the homepage, then use your own API key for REST or MCP once you are ready to integrate.