Claude MoSPI connectorWhat Claude can do with India's official statistics.
The Claude MoSPI connector exposes 4 tools, all 4 read. 0 write, 0 undocumented. Claude queries the public datasets of India's statistics ministry in four chained steps. Here's what it fetches, the order it follows, and where it trips.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you work on India's economy
India's Ministry of Statistics and Programme Implementation publishes the country's official numbers (GDP, inflation, employment, industrial output, health, energy, trade) through its eSankhyiki portal. With this connector you ask Claude the question and it pulls the series itself, instead of you clicking through the portal's menus.
Find the right dataset. step1_know_about_mospi_api starts with an overview of every available dataset and its coverage, so Claude can pick the right one.
Narrow down to an indicator and its filters. step2_get_indicators lists what a dataset measures, then step3_get_metadata returns the valid filter values (states, years, quarters) for the indicator you chose.
Get the numbers. step4_get_data finally fetches the statistics using the filters gathered in the previous step. All of it comes straight from the ministry's own eSankhyiki portal.
What Claude won't do here: all four tools on the sheet read public data, there's no account to write to. It doesn't start anything on its own, and skipping steps isn't safe: the publisher warns that bypassing the filter step yields invalid codes. A pull on a schedule is a job for an automation tool, a different line of work, listed on the Integrations hub.
Five words before you start
Quick definitions so the rest of the page reads cleanly.
- Connector
- The link you set up one time between Claude and an outside service, so Claude can use it while it answers your questions.
- Tool
- One named capability a connector gives Claude. Claude decides which ones to call, and the directory sheet lists each by its name.
- Authorization
- A service's sign-in screen where you grant Claude access. For MoSPI, our check of the server found no personal account to link at all.
- Approval
- The confirmation Claude waits for before finishing an action that changes an account, shown in the chat at the moment it counts.
- MCP
- The shared standard connectors are built on: it's what lets an assistant like Claude exchange requests with an outside service.
Set up the Claude MoSPI connector in three steps
- 01
Locate MoSPI in settings
Open Claude's settings, go to Customize then Connectors, and find MoSPI in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it for the organization first.
- 02
Start the connection
Click Connect on the MoSPI row. If the connection ever misbehaves, cut it with Disconnect and add it again: that's the intended fix for a broken link.
- 03
Check what shows up
When we checked, MoSPI's server answered without asking for any login, so there's no personal account to link. If an authorization screen does appear, read it before you accept: that screen decides what the access covers.
The 4 MoSPI tools, in the order Claude calls them
MoSPI gives Claude 4 tools: 4 that read your account, 0 that change something in it.
Four reads that chain together, from overview to raw figures. Names stay as the sheet shows them.
- 4 read
What Claude can look up (4)
4 toolsFour read steps over public data. The server flags each one as having no modifying effect.
step1_know_about_mospi_api
The entry point. It returns every MoSPI statistical dataset with a description and its coverage, so Claude can tell which one answers your question.
step2_get_indicators
Once a dataset is chosen, Claude gets its full list of indicators. You see what's measured before asking for a single number.
step3_get_metadata
Returns the valid filter values for one indicator (states, years, quarters) plus the parameters to pass back unchanged in the next call.
step4_get_data
The last step: Claude retrieves the statistical values themselves, using the filters it got just before. This is where the series you asked for finally appears.
What Claude checks with you first
By default, Claude stops and asks before every action it takes on an account for you. Here, all four tools read public data.
No source describes a MoSPI-specific confirmation, so the default rule covers its tools. On Team and Enterprise, workspace owners choose whether members may let some actions through without being asked again. They can also restrict a connector for the whole organization or leave it switched off. And the server labels each of the four tools as a read, which still doesn't replace an approval rule or an owner's restriction.
Which plans include it
None of the 819 sheets in the official directory shows plan availability. For any single connector, that information isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization. For MoSPI's current status, its sheet in the official directory is the only reliable place to look.
Where the MoSPI connector stops
A connector isn't an automation. Claude calls these tools while it answers you, and nothing fires when the ministry releases a new figure.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's docs have a page for it. All four tools read, yet a read-only list is an observed floor, not a guarantee. The directory badge isn't a security audit, and Anthropic doesn't vouch for how a publisher's tools behave, so connect only publishers you know. A community connector, once added, gets exactly the same access as any other. And because of the tool rename, Claude may show either the old or the new name.
Need help connecting MoSPI to Claude?
A person reads every message.
