MoSPI MCP Server provides AI agents access to official Indian government statistics from the Ministry of Statistics and Programme Implementation, covering 500+ indicators across employment, prices, industry, national accounts, health, education, trade, and more.
Claude is Anthropic's AI assistant, available as a desktop app and in Cowork. It supports custom connectors, so it can call MCP servers directly from a chat.
This guide connects MOSPI MCP to Claude Desktop through MewCP, so Claude Desktop can use MOSPI MCP's 4 tools, like get_indicators, get_metadata and get_data.
MOSPI MCP needs no credentials, but every call still runs through MewCP: scoped, checked and logged like any other.
More apps
Full Google Search Console control for search analytics, sitemaps, sites, and URL inspection, directly from your AI workflows. This MCP server exposes the Google Search Console API for querying search traffic data, managing sitemaps and site properties, and inspecting the indexing status of any URL. It is built for SEO teams monitoring search performance, developers automating sitemap and property management, and analysts pulling search traffic data into reporting pipelines.
Manage courses, assignments, rosters and student activity within Google Classroom. Create learning workflows, track submissions and organize educational content across classrooms.
AI's impact on real-world sectors, as a structured record for agents: source-linked headlines placed in one of 18 sectors (healthcare, law, retail, government, defense and more), with outlet, country and time, since June 2026
Hex MCP Server lets AI agents analyze data in Hex through natural-language Threads, search projects, retrieve analysis results and visualizations, and— with editing access—create, edit, and run SQL, Python, and Markdown notebooks.
Other clients
MOSPI MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact MOSPI MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
In Claude, open Settings → Connectors, then choose Add custom connector.
Name it "mewcp" and paste the URL.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Returns the full list of available indicators for a given dataset. Datasets often have broader coverage than expected — for example, ASI covers 57 indicators (capital structure, wages, employment, GVA, fuel consumption), and GENDER covers 147 indicators across health, education, labor, and crime. For PLFS and ASUSE, indicators are grouped by frequency_code: - PLFS frequency_code=1 (Annual): all 8 indicators including wages - PLFS frequency_code=2 (Quarterly): indicators 1-3 only - PLFS frequency_code=3 (Monthly): indicators 1-3 only frequency_code selects the indicator set, not time granularity. Step 2 of: list_datasets → get_indicators → get_metadata → get_data
Returns the valid filter values (states, years, quarters, etc.) for a given dataset and indicator. Filter codes are arbitrary and dataset-specific — for example, PLFS state_code 99 means "All India", and NAS frequency_code 1 means "Annual". These values cannot be inferred or guessed from parameter names alone. The returned filter_values and api_params should be used as-is when calling get_data. Step 3 of: list_datasets → get_indicators → get_metadata → get_data
Fetches statistical data from a MoSPI dataset. This is the final step of the workflow. It requires filter values from get_metadata — filter codes are arbitrary (e.g., indicator_code=3 means "Unemployment Rate" in PLFS but something different in other datasets). All filter parameters including limit and page go inside the filters dict, not as top-level arguments. Step 4 of: list_datasets → get_indicators → get_metadata → get_data
Returns an overview of all MoSPI statistical datasets with descriptions and coverage. This is the starting point ΓÇö call this first to identify the right dataset. The API covers 500+ indicators across employment, prices, industry, national accounts, health, education, disability, housing, environment, trade, and more. Each dataset has its own indicator codes, filter parameters, and valid values ΓÇö these are not standardized and cannot be inferred or guessed from parameter names alone. Four-step workflow (each step depends on the previous): 1. list_datasets() ΓÇö identify the dataset 2. get_indicators(dataset) ΓÇö list available indicators 3. get_metadata(dataset, indicator_code) ΓÇö retrieve valid filter values 4. get_data(dataset, filters) ΓÇö fetch the data Returns: dict with 'datasets' (name, description, use_for for each dataset) and 'workflow' (the four-step sequence).
