Using Demostatics with AI Assistants (draft)

Before publishing

• Not built. There is no MCP server and no AI access to Demostatics data today.
• Depends on API for Partners existing first: an MCP server is a thin, read-only layer over the same API, keys and rate limits.
• Decide which plans include it, and what users may do with data an assistant reads (same rules as the API).

The Model Context Protocol (MCP) is an open standard that lets AI assistants call external tools. The Demostatics MCP server lets an assistant you already use look up Demostatics data while it answers your questions — for example “compare the latest inflation indicators for Türkiye and Greece” or “summarise this week’s reports on Black Sea shipping”.

What the assistant can do

The server is read-only. Planned tools:

Tool	What it does
search_reports	Find reports by place, category and date
get_report	Read one report
get_latest_values	Latest Database values for a place and category
list_places / list_categories	Browse the geography and category lists

It cannot post, vote, change your account or see other users’ data.

Connecting

TODO when built: the server address (e.g. https://mcp.demostatics.com), how to add it in each assistant, and signing in with your Demostatics account (OAuth) or an API key.

Usage and limits

Each tool call counts against your plan’s API limits. TODO: numbers.

Accuracy

Assistants can misread or over-summarise data. Check important figures against the Database or the original report; every result the server returns includes a link to its source page.