Skip to main content
Glama
deenesjakoruzh
joshua-bailey

eiu-mcp-server

by joshua-bailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

eiu-mcp-server

A Model Context Protocol server that gives Claude (or any MCP-compatible LLM client) structured, token-efficient access to the EIU data API — around 200 countries and 320 economic indicator series, history and forecasts.

It exposes three tools:

Tool

Purpose

eiu_browse

List available geographies and series, optionally filtered by keyword

eiu_search

Keyword search across the series catalogue (e.g. "current account")

eiu_get_data

Fetch data by country and series code, with frequency and date filters

Reference data is fetched once per session and cached in memory, so browse and search cost no further API calls.

Prerequisites

  • EIU API Developer Portal access. This is not self-service. Email economicssupport@economist.com and ask for Developer Portal access. They will set up your account by hand. You need all three of: your portal email address, your portal password, and the API key shown in the portal.

  • uv installed on your machine. One-liner:

    curl -LsSf https://astral.sh/uv/install.sh | sh

You do not need to clone this repo or manage a virtual environment — uvx handles everything from the git URL.

Related MCP server: EODHD MCP Server

Install

Claude Code

The one-line install, run from a folder whose .env holds your three EIU values. The shell reads them, so the credentials never appear in your conversation:

set -a; source .env; set +a
claude mcp add --scope user eiu \
  -e EIU_API_KEY="$EIU_API_KEY" \
  -e EIU_EMAIL="$EIU_EMAIL" \
  -e EIU_PASSWORD="$EIU_PASSWORD" \
  -- uvx --from git+https://github.com/joshua-bailey/eiu-mcp-server.git eiu-mcp-server

Or add the entry to .mcp.json by hand:

{
  "mcpServers": {
    "eiu": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/joshua-bailey/eiu-mcp-server.git",
        "eiu-mcp-server"
      ],
      "env": {
        "EIU_API_KEY": "${EIU_API_KEY}",
        "EIU_EMAIL": "${EIU_EMAIL}",
        "EIU_PASSWORD": "${EIU_PASSWORD}"
      }
    }
  }
}

Then restart Claude Code. The three eiu_* tools should appear under /mcp.

Claude Desktop

Same JSON snippet, placed under mcpServers in:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Claude Desktop does not expand ${VAR} references, so put the literal values there instead.

Pinning a version

uvx installs the latest commit on main by default. To pin to a tagged release, append @<tag> to the git URL, e.g.:

"git+https://github.com/joshua-bailey/eiu-mcp-server.git@v0.1.0"

Environment variables

Variable

Required?

Purpose

EIU_API_KEY

Yes

Your EIU API key from the Developer Portal.

EIU_EMAIL

Yes

The email address your portal account uses.

EIU_PASSWORD

Yes

Your portal password.

All three are needed. The server logs in with the email and password to obtain a bearer token, then sends that token alongside the API key on every request. The token is cached in memory and refreshed before it expires.

Using it

Once the MCP is registered, ask Claude things like:

  • "Search EIU for current account balance series"

  • "What EIU series codes cover consumer prices?"

  • "Pull EIU annual GDP growth (DGDP) for the US, UK and China from 2015 to 2030"

  • "Show me EIU quarterly inflation forecasts for Brazil, Mexico and Chile"

Claude picks the right tool and calls it.

Codes

  • Geographies are ISO two-letter codes in capitals: US, GB, CN, BR.

  • Series are EIU's own short codes in capitals, e.g. DGDP, DCPI. Use eiu_search or eiu_browse to find them rather than guessing.

  • Frequency is one of Yearly, Quarterly or Monthly.

eiu_get_data caps its response at 200 data points to stay token-efficient and says so when it truncates. Narrow the date range or the country list to see the rest.

API reference

The underlying API is documented at developer.eiu.com/help/overview. The server talks to https://api.eiu.com/v1.

Licence

MIT — see LICENSE. Applies to the wrapper code in this repository only. Dependencies retain their own licences. EIU data is a paid subscription and its terms of use apply independently of this wrapper.

Available Tools

3 tools
eiu_browseA

Browse available EIU geographies and data series.

Call with no filter to see all available geographies/series. Use filter to narrow results by keyword.

Args: filter: Optional keyword (e.g. 'Brazil', 'GDP', 'inflation') show: 'geographies', 'series', or 'both' (default)

ParametersJSON Schema
NameRequiredDescriptionDefault
showNoboth
filterNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden. It explains what happens with no filter versus with a filter and describes the show options. It does not mention output format or pagination, but the presence of an output schema reduces the need for that detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-organized: a summary line, short usage guidance, and a clean args list. Every sentence contributes value, with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter browse tool, the description is complete. It covers all parameters, defaults, and core behavior, and the output schema exists to document return values. The lack of explicit sibling routing is the only minor omission, but the intended use is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description fully compensates. It defines filter as an optional keyword with concrete examples, and show as selecting 'geographies', 'series', or 'both' with the default noted. This is meaningful semantic content beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Browse available EIU geographies and data series.' This clearly distinguishes it from siblings like eiu_get_data and eiu_search, which presumably retrieve or search data rather than browse the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operational context: 'Call with no filter to see all available geographies/series. Use filter to narrow results by keyword.' It explains how to use the tool and the effect of each parameter, though it does not explicitly state when to prefer eiu_search or eiu_get_data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

eiu_get_dataA

Fetch EIU forecast/indicator data by country and series codes.

Use eiu_browse or eiu_search first to find valid codes.

Args: geography_codes: ISO 2-char codes (e.g. ['US', 'BR', 'CN']) series_codes: EIU series codes (e.g. ['DGDP', 'DCPI']) frequency: 'Yearly', 'Quarterly', or 'Monthly' min_date: Start date YYYY-MM-DD (default: 5 years ago) max_date: End date YYYY-MM-DD (default: 5 years ahead)

ParametersJSON Schema
NameRequiredDescriptionDefault
max_dateNo
min_dateNo
frequencyNoQuarterly
series_codesYes
geography_codesYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It clearly implies a read-only fetch operation, states the prerequisite of finding valid codes first, and documents default date ranges and accepted frequency values. It could add error/rate-limit behavior, but the default date behavior and non-destructive nature are usefully conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured. The high-level purpose is front-loaded, the prerequisite is stated in a single sentence, and the Args block is clean and easy to scan. No sentence is wasted or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema, return-value documentation is not needed. The description covers all five parameters, provides valid examples, explains the required discovery workflow, and states defaults. Everything an agent needs to invoke the tool correctly is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates. It explains every parameter: ISO 2-char geography codes with examples, EIU series codes with examples, allowed frequency values, and date format/defaults for min_date and max_date. This is far beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Fetch') and a specific resource ('EIU forecast/indicator data') with clear scope by country and series codes. This distinguishes it well from the sibling tools eiu_browse and eiu_search, which are for finding codes rather than retrieving data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly explains the intended workflow: use eiu_browse or eiu_search first to find valid codes, then call this tool. This is clear guidance on when to use this tool versus the alternatives, leaving no ambiguity for the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updatesv0.1.0
    • First observedeiu_browse
    • First observedeiu_get_data
    • First observedeiu_search
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation3/5

eiu_browse and eiu_search both support keyword-based series discovery, so agents may be unsure which to call when looking up series codes. eiu_browse is broader because it also covers geographies, while eiu_search is narrowly focused on series, but the boundary is somewhat blurred. eiu_get_data is clearly distinct.

Naming Consistency4/5

All tools share the eiu_ prefix and use lower_snake_case, making the naming pattern predictable. However, eiu_browse and eiu_search are bare verbs while eiu_get_data is verb_noun, which is a minor inconsistency.

Tool Count4/5

Three tools is a reasonable, compact set for a browse/search/fetch data workflow. The count is appropriate, though eiu_browse and eiu_search overlap enough that the set could arguably be reduced to two tools.

Completeness4/5

The core workflow of discovering geographies and series, then fetching EIU data, is covered without dead ends. Minor gaps exist around metadata details or available date ranges, but agents can complete the primary task effectively.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • econstats-mcp

    joshfwaldman1
    F
    license
    Not graded
    quality
    D
    maintenance
    Economic data MCP server that connects FRED, BLS, BEA, IMF, World Bank, and ECB to any MCP-compatible client, with built-in methodology rules to guide LLMs in selecting appropriate economic indicators.
    -
  • EODHD MCP Server by EodHistoricalData

    EODHD MCP Serverofficial

    EodHistoricalData
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables interaction with EOD Historical Data APIs, providing access to 75 read-only tools for financial data including fundamentals, news, screeners, and options via MCP transports.
    20
    MIT

  • world-bank-server

    gu-dsan6725
    F
    license
    Not graded
    quality
    D
    maintenance
    Exposes World Bank development data and country information via MCP resources and tools, enabling AI agents to query historical indicators and live API data.
    -