MewCP LogoAStheTech
MCPs
Use Cases

Use cases by category

Productivity & InboxInbox, calendar, and daily flowEngineering & DevOpsShip, debug, and run on-callSales & CRMPipeline, outreach, and dealsMarketing & GrowthCampaigns, SEO, and growthSupport & SuccessTriage tickets, keep customers happyFinance & OpsClose, reconcile, and expensesCreative & ContentGenerate assets and contentPeople & HiringHiring, onboarding, and HRResearch & DataSynthesize data and insights
See all use cases
Resources
BlogsProduct updates and storiesArticlesIntegration guides and code examples
PricingDocsSign in
MewCP Logo

Infrastructure You Can Trust for Agentic Products

X

Categories

  • Productivity & Docs
  • Developer Tools
  • CRM & Sales
  • Finance & Commerce
  • Data & Analytics
  • Marketing & SEO
  • Search & Web
  • Communication
  • View All Servers →

Resources

  • Blog
  • Docs
  • Privacy Policy
  • Terms of Service

Blogs

  • View All Blogs →

Articles

  • View All Articles →
Browse Servers|Pricing|Contact

Browse by Category

Productivity & Docs

  • Gmail
  • Google Drive
  • Google Classroom
  • Google Calendar
  • Google People
  • YouTube
  • Notion
  • ClickUp
  • Figma
  • Google Tasks
  • Cal
  • Monday
  • Luma
  • Notion MCP
  • Mem MCP
  • Linear MCP
  • Calendly MCP
  • Consensus MCP
  • Craft MCP
  • Close MCP
  • Dice MCP
  • Lumin PDF MCP
  • Develop21 MCP
  • Granola MCP
  • Lucid MCP
  • Mermaid Chart MCP
  • Fireflies MCP
  • ClickUp MCP
  • Miro MCP
  • Llamaindex MCP

Developer Tools

  • Gemini
  • Veo
  • ClickUp
  • Firecrawl
  • Vercel
  • Apify
  • Github
  • HTTP
  • Chef
  • Scientific Calculator
  • Figma
  • Perplexity
  • Apify MCP
  • Hugging Face Hub MCP
  • Buildkite MCP
  • Cloudflare MCP
  • Context7 MCP
  • Ahrefs MCP
  • Sentry MCP
  • Brevo Docs MCP
  • X Docs MCP
  • Jev
  • Linear MCP
  • Calendly MCP
  • Craft MCP
  • DeepWiki MCP
  • Inspo MCP
  • Kernel MCP
  • Malwarebytes MCP
  • Mermaid Chart MCP
  • Supabase MCP
  • Microsoft Learn MCP
  • Webflow MCP
  • Scalar Docs MCP
  • Oneuptime MCP
  • Redocly MCP
  • Reducto Docs MCP
  • Llamaindex Docs MCP

CRM & Sales

  • Google People
  • OneSignal MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • Carbon Voice MCP
  • Clay MCP
  • Close MCP
  • Attio MCP
  • Clarify MCP

Finance & Commerce

  • Razorpay
  • Polymarket
  • Kite
  • Stripe
  • Binance
  • Upstox
  • Aiwyn MCP
  • Era-Context-MCP
  • Granted MCP
  • XDC AI MCP
  • Agentery MCP
  • Agent Embassy
  • Quick Commerce MCP
  • Longbridge MCP
  • Mercury MCP

Data & Analytics

  • Apify MCP
  • Cloudflare MCP
  • Ahrefs MCP
  • Candid MCP
  • Consensus MCP
  • Contentsquare MCP
  • Era-Context-MCP
  • Instinct MCP
  • legal Data Hunter MCP
  • Marcopolo MCP
  • Mixpanel MCP
  • MOSPI MCP

Marketing & SEO

  • Mailchimp
  • Google Business
  • YouTube
  • Google Search Console
  • OneSignal MCP
  • Cloudflare MCP
  • Brevo Docs MCP
  • Brevo
  • Brevo MCP
  • AirOps MCP
  • Clay MCP
  • Contentsquare MCP
  • Reelsmith MCP
  • GoDaddy MCP
  • Metricool MCP
  • Webflow MCP
  • Windsor MCP
  • Commonroom MCP

Search & Web

  • Web Scrapper
  • Firecrawl
  • Apify
  • Perplexity
  • Context.dev
  • Exa
  • Brave Search
  • Apify MCP
  • Ahrefs MCP
  • DeepWiki MCP
  • Dice MCP
  • GoDaddy MCP
  • Granted MCP
  • Microsoft Learn MCP
  • Viator MCp

Communication

  • Gmail
  • Google Meet
  • Mailchimp
  • Google Calendar
  • WhatsApp
  • Slack
  • OneSignal MCP
  • Brevo Docs MCP
  • Carbon Voice MCP

© 2026 MewCP. All rights reserved.

  1. Home
  2. MCPs
  3. MOSPI MCP
MOSPI MCP

MOSPI MCP Integration for AI Agents

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.

v2.3.04 toolsNo auth
Open in ChatGPTChatGPT
Open in ClaudeClaude
Playground
VS CodeVS Code
Connected to MOSPI MCP via MewCP.

Encrypted at rest, isolated from the model

Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.

Try asking

Everything MOSPI MCP can do

Tools4

get_indicators

read

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

read

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

get_data

read

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

list_datasets

read

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).

Connect MOSPI MCP to your agent

One endpoint, the same key, whichever client you use.

Apps

SDKs

Claude Desktop

Claude Desktop

~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)

JSON
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization: Bearer API_KEY"
      ]
    }
  }
}

Replace API_KEY with your own key.

Already have an "mcpServers" section in your config? Just add the server entry inside it.

  1. 01Open Claude Desktop → Settings → Developer → "Edit Config"
  2. 02Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
  3. 03Save the file and restart Claude Desktop
  4. 04Start a new conversation — your tool will be available

One endpoint. Every service.

VS CodeAny agent
One Gateway

Apify MCP

OAuth

Cloudflare MCP

OAuth

Ahrefs MCP

OAuth

MOSPI MCP

No auth

Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you

Separate connections░░░░░░░░░░░░░░░░░░░░░░░░░░░░174 tool definitions ~38k tokensWith MewCP░░░░░░░░░░░░░░░░░░░░░░░░░░░░4 meta-tools ~3.0k tokens

Built for AI agents

MOSPI MCP runs through a gateway that holds the credentials, scopes the access and records every call.

Nothing to connect

  • MOSPI MCP needs no credential, so there is no key to issue, store or rotate.
  • Add it to a toolset and start calling tools.

Credentials stay out of context

  • MOSPI MCP credentials are resolved at the gateway and attached to the outbound call.
  • The agent sees tool results, never a token.
  • Revoke an account and the next call stops working — no redeploy.

Scoped access, fully logged

  • Choose exactly which MOSPI MCP tools an agent is allowed to call.
  • Every call is logged with its outcome, latency and which account it ran as.
  • Catalog changes are reviewed before they ship, so tool descriptions cannot shift under you.

One endpoint for every server

  • Reach MOSPI MCP through the same MCP endpoint as the rest of your toolset.
  • Tools are discovered on demand, so 4 tools do not fill the context window.
  • Stateless: no sessions to keep alive and no reconnect logic.

Ready to connect MOSPI MCP?

Managed auth, hosted MCP servers, and every Gmail tool your agent needs.

Free to start.