Use MoSPI MCP with
Sokko.
Connect MoSPI MCP and tell Sokko what to do. It runs the actions you ask for and reacts to what happens. No workflows, no code.
Works with 1,000+ tools · No code required
Actions
Everything Sokko can do in MoSPI MCP
Every MoSPI MCP action Sokko can run. Ask for one in a sentence and it's done.
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
Get indicators
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
Get metadata
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
List datasets
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).
Get connected
Live in your Slack in two minutes.
No workflows to wire up. Turn on the tools you already use, and your agent gets to work.
Add to Slack
1
Add Sokko to Slack
One click from the Slack marketplace. Your whole team gets Sokko at once.
2
Connect your tools
Sokko works with 1,000+ apps and any MCP server.
Martin
9:53 AM
@Sokko
What can you do with MoSPI MCP?
3
Put Sokko to work
@mention Sokko in any channel and it gets going. Minutes, not a weekend.
Questions, answered.
Sokko is an AI assistant that lives in your Slack. Connect your apps, ask for what you need in plain language, and Sokko takes the work off your plate.
This toolkit does not require authentication and has no account connection flow. Check its documented usage options before using it through this agent.
No. There's nothing to build or configure. You ask Sokko in Slack the same way you'd ask a colleague, and Sokko handles the rest.
Yes. Ask once and tell Sokko when to repeat it, like every Monday at 9am, and it becomes a routine that runs without you.
Read and act on data in MoSPI MCP, and trigger workflows when something changes there. Tell Sokko the outcome you want and it handles the rest.
Yes. Sokko connects to 1,000+ apps and any MCP server, so you can ask for tasks that span MoSPI MCP and the rest of your stack in a single request.