MCP.so
Sign In

Anthropic Economic Index MCP Server

@Anthropic Economic Index

Basic information

Transport

streamable-http

Authentication

Check provider docs

Category

Data & Analytics

Author

Anthropic Economic Index

About Anthropic Economic Index MCP Server

Anthropic's official MCP server for the Anthropic Economic Index, its open research dataset on how people use Claude. Assistants can rank countries and US states by Claude usage, break usage down by occupation and work task, compare regions and read methodology notes. The data is CC BY 4.0, and the server is free and needs no sign-in.

Connection details

https://econ-index.mcp.claude.com/mcp

Setup

claude mcp add anthropic-economic-index --transport http https://econ-index.mcp.claude.com/mcp

Anthropic Economic Index MCP Server tools

9

Anthropic Economic Index overview: coverage, releases, definitions. Call this once at the start of an exploration. Returns the latest data period and snapshot timestamp, dataset metadata (license, publisher, landing page), temporal_coverage — the published period span; the served numbers are a snapshot of the latest period, not a trend — geography and occupation coverage counts, the worldwide headline split, and a definitions glossary to reuse when presenting numbers to non-experts. country_count counts only countries with a published Anthropic Usage Index, the same cohort econ_index_list_countries / econ_index_get_usage_by_country cover. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

One country's subregions ranked by Claude usage. Defaults to the USA: all 50 states plus Washington, D.C., ranked by the Anthropic Usage Index. Other countries' subregions have no published index — rows rank by usage_share_pct, each subregion's share of the country's observed usage; that is volume, not engagement relative to population size, and map colors should say so. Each row carries the use-case splits, top-5 job categories, top artifact types, and its top-5 request topics with shares — enough for a choropleth with tooltips and a click-through panel from this single call. For one subregion's top-10 categories and full hierarchies, use econ_index_get_usage_by_subregion. For US states, join a us-atlas states topojson by state name (Washington, D.C. is 'District of Columbia' there) and color by anthropic_usage_index; elsewhere search for a suitable topojson when none is at hand and color by usage_share_pct. To compare subregions, compare profiles (each one's categories and topics vs the national average: baseline_pct, vs_baseline_index), not just usage volume. When a visualization tool is available, always visualize: this data is geographic, so lead with a choropleth of a numeric field — the usage index or a split share; a map of each region's top topic or category comes out near-uniform, because the same entries lead nearly everywhere — when no map source for these regions is bundled or known, search for one before any non-map fallback; more than one visualization is fine. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Full Claude-usage profile for one subregion (state, province, prefecture). Covers US states and, where published, other countries' subregions (BR-SP, JP-13, ...). Returns the usage rank within the country, the augmentation/automation and work/personal/coursework splits, top-10 job categories, most frequent request topics, work tasks, and artifact types. The key shares carry the country average alongside (baseline_pct, vs_baseline_index), and the baseline block carries the country's headline figures for side-by-side display. US states also carry the Anthropic Usage Index; other subregions have no published index — present their standing by rank and share, never a made-up index. Pass include_tasks / include_requests for the full occupation-task and request-topic hierarchies (each node carries its 0-100 share of the subregion's usage). Empty lists mean not published — never invent entries. Open with the headline numbers against the country average, then visualize the job categories, then the most frequent topics, then artifact types. When a visualization tool is available, always explore visualizations: consider the data's shape — how many series, whether values carry a baseline comparison, whether anything is geographic — try the available options and judge which fits best; more than one visualization is fine. Geographic data gets a choropleth by default. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Every country with a published Anthropic Usage Index, ranked by it. Each row carries the index and rank, the augmentation/automation and work/personal/coursework splits, the top-5 job categories, top artifact types, and its top-5 request topics with shares — enough for a choropleth with tooltips and a click-through panel from this single call. iso_numeric matches the feature ids of a world topojson (world-atlas countries-110m): join the map on codes, not country names. For one country's top-10 categories and full hierarchies, use econ_index_get_usage_by_country. Lead with a world choropleth colored by anthropic_usage_index; give tooltips the index plus the top job categories or the use-case split. Follow with the top job categories — a country ranking complements the map rather than replacing it. To compare countries, compare profiles (each one's categories and topics vs the global average: baseline_pct, vs_baseline_index), not just usage volume. When a visualization tool is available, always visualize: this data is geographic, so lead with a choropleth of a numeric field — the usage index or a split share; a map of each region's top topic or category comes out near-uniform, because the same entries lead nearly everywhere — when no map source for these regions is bundled or known, search for one before any non-map fallback; more than one visualization is fine. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Full Claude-usage profile for one country. Returns the usage index and rank, the augmentation/automation and work/personal/coursework splits, top-10 job categories, most frequent request topics, work tasks, and artifact types. The key shares carry the global average alongside (baseline_pct, vs_baseline_index), and the baseline block carries the global headline figures for side-by-side display. Pass include_tasks / include_requests for the full occupation-task and request-topic hierarchies (each node carries its 0-100 share of the country's usage). Only countries with published usage are covered. Open with the headline numbers against the global average. For any single-country question, follow up with econ_index_list_subregions for the within-country picture — coverage varies and an empty result says so; where rows exist, lead with the subregion choropleth. Then visualize the job categories, then a brief mention of topics, then artifact types. When a visualization tool is available, always explore visualizations: consider the data's shape — how many series, whether values carry a baseline comparison, whether anything is geographic — try the available options and judge which fits best; more than one visualization is fine. Geographic data gets a choropleth by default. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Occupations and job categories ranked by Claude usage of their tasks. A bare call returns category_shares — every job category with its share of global usage. Lead with those ~22 categories — one ranked series of shares — and visualize them, narrating only the top few. Pass query to drill down: a category name lists its occupations, an occupation name returns that occupation, and any other word matches occupation names. When no slice exists for the exact profession asked, quote the closest published figure with its scope named ('software developers', 'Legal as a whole') — never present broader numbers as the requested slice. Tasks in the gap between task_count and published_task_count are not published; their values may be zero. Global scope only — for one state or country use econ_index_get_usage_by_subregion / econ_index_get_usage_by_country. Answers questions like 'which jobs and careers use AI the most?'. Frame results as "AI is used for tasks commonly done by [occupation]", never "[occupation]s are using AI" — the people in these conversations are often not members of that occupation. When a visualization tool is available, always explore visualizations: consider the data's shape — how many series, whether values carry a baseline comparison, whether anything is geographic — try the available options and judge which fits best; more than one visualization is fine. Geographic data gets a choropleth by default. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Side-by-side headline comparison of 2-8 regions from one cohort. Returns each region's usage index, augmentation/automation split, work/personal/coursework split, top job categories, most common request topics, and top work tasks, plus the shared baseline (the world for countries; the country for its subregions). Regions publish different work-task subsets — compare tasks by name, not rank position. Compare countries with countries, or subregions of one country — indexes are normalized within one cohort and never compare across cohorts, and subregion usage shares are likewise calculated within the parent country. For region profiles beyond the headline, use the detail tools; for a full ranking, the list tools. When a visualization tool is available, always build comparative visualizations — show each region relative to the others and the shared baseline: heatmaps, diverging bar charts, bubble charts, and grouped or stacked bars all fit side-by-side data; go beyond a single bar chart or choropleth, and more than one visualization is fine. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Top work tasks worldwide: what people use Claude for the most, by task. Returns the top 50 work tasks, ranked by their 0-100 share of global sampled conversations. Task descriptions come from O*NET, the US government's catalog of each occupation's tasks, in plain English, and are matched from conversation content. For the breakdown within one occupation, use econ_index_get_occupation_usage. Answers questions like 'what do people in different careers actually use Claude for?'. Task wording is specific enough that questions about one kind of request — financial advice, resume help, lesson planning — often match tasks here directly. When a visualization tool is available, always explore visualizations: consider the data's shape — how many series, whether values carry a baseline comparison, whether anything is geographic — try the available options and judge which fits best; more than one visualization is fine. Geographic data gets a choropleth by default. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Global Claude usage, occupational task breakdowns, and common request topics. How people use Claude overall including occupational task breakdowns and common request topics — the Anthropic Economic Index worldwide profile. Returns the augmentation/automation and work/personal/coursework splits, the classifier-estimated task-time comparison (hours working alone vs minutes with Claude — normalize the units before charting), top job categories, top request topics, and artifact types. Topic-share questions — how often people ask about money, health, investing, travel, and the like — are answered by top_request_topics, and the worldwide work-task ranking (econ_index_list_top_work_tasks) carries the task-level detail behind the same questions. Whenever the question warrants a country breakdown, call econ_index_list_countries and lead with the world choropleth (its rows carry iso_numeric for a code join), with this profile's splits as compact metric badges above the map; then visualize the job categories. When a visualization tool is available, always explore visualizations: consider the data's shape — how many series, whether values carry a baseline comparison, whether anything is geographic — try the available options and judge which fits best; more than one visualization is fine. Geographic data gets a choropleth by default. Figures are derived from anonymized, aggregated conversation content and cannot be tied to individual users. They describe observed Claude usage by task and are not evidence about employment or job automation.

Overview

What is Anthropic Economic Index MCP Server?

Anthropic Economic Index MCP Server is Anthropic's official, free endpoint (https://econ-index.mcp.claude.com/mcp) that lets AI assistants explore the Anthropic Economic Index, Anthropic's public data on how people around the world use Claude, by country, US state, occupation and task.

The Anthropic Economic Index is a research initiative on AI's effects on the economy. It matches aggregated Claude conversations to job tasks and publishes the results as reports and open datasets under a CC BY 4.0 license. The MCP server puts that dataset behind a conversational interface, so researchers, journalists, policy analysts and curious users can ask "Which occupations use AI the most?" and get figures straight from the source. Anthropic lists it in the Claude connector directory as an Anthropic-built connector.

How to use Anthropic Economic Index MCP Server?

No account, API key or sign-in is needed for the server itself. Add it by URL:

https://econ-index.mcp.claude.com/mcp

Claude Code

claude mcp add --transport http economic-index https://econ-index.mcp.claude.com/mcp

Claude Desktop and claude.ai

The connector is listed in the Claude directory as "Anthropic Economic Index". Open the connectors menu in claude.ai settings, find it in the directory and enable it; after that it works in any conversation. You can also add it as a custom connector with the URL above.

Cursor

{
  "mcpServers": {
    "economic-index": {
      "url": "https://econ-index.mcp.claude.com/mcp"
    }
  }
}

VS Code

{
  "servers": {
    "economic-index": {
      "type": "http",
      "url": "https://econ-index.mcp.claude.com/mcp"
    }
  }
}

Key features of Anthropic Economic Index MCP Server

  • Official server published by Anthropic, with data licensed CC BY 4.0.
  • Free and open: no authentication required.
  • Geographic coverage of more than 120 countries plus all 50 US states and Washington, D.C., at the time of writing.
  • Occupation and task data: around 22 job categories and several hundred published occupations, with task descriptions drawn from O*NET.
  • Usage splits such as augmentation versus automation, and work versus personal versus coursework use.
  • Built-in methodology notes and definitions, so the assistant can present the numbers with the right caveats.
  • Tool outputs designed for visualization, such as ISO country codes for building a world map.

Anthropic Economic Index MCP Server tools

The server exposes nine tools, all prefixed econ_index_:

  • Start here: econ_index_get_dataset_overview returns coverage, the latest data period, license, definitions and the global headline split. It is meant to be called once at the start of an exploration.
  • Global view: econ_index_get_global_usage returns the worldwide profile, and econ_index_list_top_work_tasks returns the top 50 work tasks people use Claude for.
  • Countries: econ_index_list_countries ranks every country with a published Anthropic Usage Index, and econ_index_get_usage_by_country returns one country's full profile.
  • Subregions: econ_index_list_subregions ranks a country's subregions (US states by default), and econ_index_get_usage_by_subregion profiles a single state, province or prefecture.
  • Occupations and comparisons: econ_index_get_occupation_usage ranks job categories and drills into occupations, while econ_index_compare_regions compares two to eight regions from the same cohort.

Use cases of Anthropic Economic Index MCP Server

  • Occupational research: "Which occupations use AI the most, and what tasks are they using it for?"
  • Regional analysis: "What are the most common ways people in Colorado use Claude?"
  • Country comparisons: "Compare Claude usage in Japan, Germany and Brazil."
  • Journalism: check a claim about AI adoption against Anthropic's published figures and cite the source.
  • Teaching and policy work: explain the difference between augmentation and automation using real usage splits.

Troubleshooting Anthropic Economic Index MCP Server

  • Numbers look like a trend but are not: the server serves a snapshot of the latest data period. It has no trend series, so it cannot show shares rising or falling over time.
  • Index values do not line up: the Anthropic Usage Index is normalized within one cohort. Compare countries with countries, or subregions of one country with each other, never across cohorts.
  • Missing values: a null means the value is not published for that cell, not necessarily that it is zero.
  • Exact profession not found: the dataset covers occupations with published usage, not the full taxonomy; use the closest published occupation or category.

Frequently asked questions

1

Is Anthropic Economic Index MCP Server official?

Yes. It is built and listed by Anthropic in the Claude connector directory and served from a claude.com domain.

2

Is it free?

Yes. The server requires no authentication, and the underlying Economic Index data is published under a CC BY 4.0 license.

3

What does the Anthropic Economic Index measure?

Observed Claude usage, with conversations matched to job tasks. Anthropic notes it reflects patterns in Claude usage, not the labor market as a whole, and cannot on its own support conclusions about job displacement.

4

Which clients does it work with?

The directory lists Claude, the Claude API and Claude Code. Because it is a standard Streamable HTTP server, it can also be added by URL in Cursor, VS Code and other MCP clients.

5

How current is the data?

At the time of writing, the server reported a latest data period of May 2026. Call `econ_index_get_dataset_overview` to see the current period.

6

Where does the data come from?

The server names anthropic.com/economic-index as the source for its numbers and methodology, and asks assistants to give users that link.

7

What is the Anthropic Economic Index remote MCP server?

The Anthropic Economic Index remote MCP server is a hosted Model Context Protocol endpoint at https://econ-index.mcp.claude.com/mcp, so AI assistants can connect to it without installing or running anything locally.

8

How do I connect to the Anthropic Economic Index MCP server?

Add the endpoint https://econ-index.mcp.claude.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

9

Does the Anthropic Economic Index MCP server require authentication?

Authentication requirements for Anthropic Economic Index have not been confirmed in this listing. Check the provider’s documentation before connecting.

10

Which transport does the Anthropic Economic Index MCP server use?

Anthropic Economic Index exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments