How do I use Government Scheme MCP Server?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Government Scheme MCP Server Search for schemes for farmers in Punjab with income below 5 lakh" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

Government Scheme MCP Server

by magicstack-llp

Overview Schema Related Servers Score Discussions

Python

Remote

Government Scheme MCP Server

A Model Context Protocol (MCP) server for accessing and managing Indian Government Schemes database. This server provides tools for searching, creating, and managing government benefit schemes with comprehensive eligibility filtering.

Features

Health Check: Verify server connectivity and API status
Scheme Search: Advanced filtering by demographics, geography, income, and eligibility criteria
Scheme Management: Create and retrieve government scheme records
Comprehensive Filtering: Support for age, gender, income, employment status, social categories, disabilities, and more

Related MCP server: Alumnx MCP Server

Installation

From PyPI (when published)

pip install gov-scheme-mcp

From Source

git clone https://github.com/magicstack-llp/gov-scheme-mcp-py
cd gov-scheme-mcp
pip install -e .

Usage

As an MCP Server

The server can be used with any MCP-compatible client:

gov-scheme-mcp

Environment Variables

GOV_API_URL: Base URL for the government schemes API (default: http://localhost:3000)

Available Tools

`health()`

Check server health and API connectivity.

Returns: JSON with connection status and API endpoint information.

`create_scheme(...)`

Create a new government scheme record with comprehensive metadata.

Parameters:

code: Unique scheme identifier
name: Scheme name
description: Detailed description
department: Government department
category: Program domain (education, health, agriculture, etc.)
benefit_type: Type of benefit (cash, subsidy, scholarship, loan, insurance, pension, grant, in-kind)
benifit_details: Detailed description of benefit structure, payouts, and timelines
terms_and_conditions: Terms and conditions text for the scheme
scheme_raw_text: Raw, unstructured text of scheme details
official_website: Official scheme website URL
application_link: Direct application form/link URL
url: Official scheme URL (legacy field)
contact: Contact information
Demographics: min_age, max_age, genders
Economic: income_min, income_max, employment_status
Social: social_categories, marital_statuses, religions, disabilities
Geographic: states, districts, urban_rural
Requirements: required_documents, caste_required, domicile_required
Status: is_active

`read_scheme(id)`

Fetch a single scheme by numeric ID.

Parameters:

id: Numeric scheme ID

`update_scheme(id, ...)`

Update an existing scheme by ID. Only provided fields will be changed.

Parameters:

id: Numeric scheme ID to update
All other fields are the same as create_scheme(...) and are optional

`delete_scheme(id)`

Delete a scheme by ID.

Parameters:

id: Numeric scheme ID to delete

`search_schemes(...)`

Search schemes with advanced filtering capabilities.

Parameters:

q: Text search in name/description
age: User age for eligibility filtering
income: User income level
gender: Gender filter (male, female, other)
employmentStatus: Employment status (unemployed, farmer, student, salaried, entrepreneur)
disabilities: Disability categories (visual, hearing, mobility, intellectual, multiple, other)
socialCategories: Social categories (SC, ST, OBC, EWS, GENERAL)
maritalStatus: Marital status (single, married, divorced, widowed)
religion: Religious affiliation
state: State/UT name
district: District name
urbanRural: Area type (urban, rural)
profession: Professional category
casteRequired: Filter by caste certificate requirement
domicileRequired: Filter by domicile certificate requirement
category: Scheme category filter
benefitType: Benefit type filter
active: Active schemes only
limit: Maximum results (default: 100)
offset: Result offset (default: 0)

Configuration for MCP Clients

Claude Desktop

Add to your claude_desktop_config.json:

{
	"mcpServers": {
		"gov-scheme-mcp": {
			"command": "gov-scheme-mcp",
			"env": {
				"GOV_API_URL": "https://your-api-server.com"
			}
		}
	}
}

Other MCP Clients

Configure the server command as gov-scheme-mcp with the appropriate environment variables.

Development

Setup

git clone https://github.com/magicstack-llp/gov-scheme-mcp-py
cd gov-scheme-mcp
pip install -e ".[dev]"

Testing

pytest

Code Formatting

black src/
isort src/

Type Checking

mypy src/

API Requirements

This MCP server requires a compatible government schemes API with the following endpoints:

GET /: Health check endpoint
POST /api/schemes: Create new scheme
GET /api/schemes/{id}: Retrieve scheme by ID
PATCH /api/schemes/{id}: Update scheme by ID (partial update)
DELETE /api/schemes/{id}: Delete scheme by ID
POST /api/schemes/search: Search schemes with filters

License

MIT License - see LICENSE file for details.

Contributing

Fork the repository
Create a feature branch
Make your changes
Add tests if applicable
Run the test suite
Submit a pull request

Support

For issues and questions:

Open an issue on GitHub
Check the documentation

Available Tools

6 tools

create_schemeA

Create a new government scheme record. Pass only valid fields; unknown fields are ignored. Returns the created row as JSON.

Args:
    code: Unique code for the scheme
    name: Name of the scheme
    description: Description of the scheme
    department: Department offering the scheme
    category: Program domain (education, health, agriculture, housing, women, child, senior, disability, minority, entrepreneurship, employment, skill, welfare)
    benefit_type: Type of benefit (cash, subsidy, scholarship, loan, insurance, pension, grant, in-kind)
    benifit_details: Detailed description of the benefit structure, payouts, timelines
    terms_and_conditions: Terms and conditions text for the scheme
    scheme_raw_text: Raw, unstructured text of scheme details scraped or provided
    official_website: Official scheme website URL
    application_link: Direct application form/link URL
    url: Official URL for the scheme
    contact: Contact information
    min_age: Minimum age requirement
    max_age: Maximum age requirement
    genders: List of allowed genders (male, female, other)
    income_min: Minimum income requirement
    income_max: Maximum income requirement
    employment_status: List of employment statuses (unemployed, farmer, student, salaried, entrepreneur)
    disabilities: List of applicable disabilities (visual, hearing, mobility, intellectual, multiple, other)
    social_categories: List of social categories (SC, ST, OBC, EWS, GENERAL)
    marital_statuses: List of marital statuses (single, married, divorced, widowed)
    religions: List of applicable religions
    states: List of applicable states/UTs
    districts: List of applicable districts
    urban_rural: List of area types (urban, rural)
    professions: List of applicable professions
    required_documents: List of required documents
    caste_required: Whether caste certificate is required
    domicile_required: Whether domicile certificate is required
    is_active: Whether the scheme is active

ParametersJSON Schema

Name	Required	Description	Default
`code`	No
`name`	No
`description`	No
`department`	No
`category`	No
`benefit_type`	No
`benifit_details`	No
`terms_and_conditions`	No
`scheme_raw_text`	No
`official_website`	No
`application_link`	No
`url`	No
`contact`	No
`min_age`	No
`max_age`	No
`genders`	No
`income_min`	No
`income_max`	No
`employment_status`	No
`disabilities`	No
`social_categories`	No
`marital_statuses`	No
`religions`	No
`states`	No
`districts`	No
`urban_rural`	No
`professions`	No
`required_documents`	No
`caste_required`	No
`domicile_required`	No
`is_active`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.1/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that unknown fields are ignored and returns the created row as JSON. However, it lacks details on failure modes, idempotency, or permissions required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with key behavior in one sentence, then provides a structured list of parameters with brief descriptions. Though lengthy due to 31 parameters, it is well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (31 params, no enum constraints), the description covers basic usage and parameter meanings. However, it does not provide guidance on minimal required fields or uniqueness constraints, leaving some gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description lists all 31 parameters with meaningful descriptions (e.g., category lists allowed domains). This fully compensates for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new government scheme record', specifying the action (create) and resource (government scheme record). This distinguishes it from sibling tools like update_scheme, delete_scheme, and read_scheme.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies use for creating new records, which is clear context. However, it does not explicitly state when not to use or suggest alternatives, such as using update_scheme for modifications.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

delete_schemeB

Delete a scheme by ID.

Args:
    id: The numeric ID of the scheme to delete

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided. The description only states the action 'delete' but does not disclose destructive effects, cascading impacts, permissions, or error behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise, two sentences with no extraneous text. However, it could be slightly more structured (e.g., add result info).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation with one parameter and an output schema, the description is minimal but functional. Lacks behavioral context like idempotency or error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description merely restates the schema: 'The numeric ID of the scheme to delete.' With 0% schema description coverage, this adds no value beyond the input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Delete a scheme by ID' with a specific verb and resource. It distinguishes from sibling tools like create, read, search, update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Implies deletion by ID but does not mention prerequisites or conditions (e.g., existence check).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

healthA

Check server health and API connectivity. Returns JSON with ok/api/error.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits. It only states the action and return format; it omits whether the call is read-only, requires authentication, has rate limits, or potential errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters and an output schema, the description is minimally adequate but lacks usage context and behavioral details for a health check tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and schema coverage is 100%. The description adds no parameter-level meaning, but the baseline for no parameters is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool verifies server health and API connectivity, specifying the returned format. This is specific and distinct from sibling tools (all scheme CRUD operations).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for health checks but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

read_schemeA

Fetch a single scheme by numeric ID.

Args:
    id: The numeric ID of the scheme to fetch

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes a simple fetch operation with no side effects, but fails to disclose behaviors like error handling or response format. The presence of an output schema reduces the need to explain return values, so the description is adequate but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, using two sentences for the overall purpose and one sentence for the parameter. Every word is necessary and there is no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no annotations, output schema exists), the description covers the essential purpose and parameter. It could be improved by noting error behavior (e.g., 404 if not found), but as it is, it is nearly complete for a basic fetch operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has one required integer parameter 'id' with no description (0% coverage). The description adds 'numeric ID' which is redundant with the schema type. It does not provide additional context such as valid ranges or how to obtain the ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Fetch a single scheme by numeric ID', using a specific verb and resource. It distinguishes from sibling tools like create_scheme, delete_scheme, update_scheme, and search_schemes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you have a numeric ID for a scheme, but does not provide explicit guidance on when to use this tool versus alternatives like search_schemes, nor does it mention when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_schemesA

Search schemes by user profile/filters. Supports various criteria for eligibility matching.

Args:
    q: Text to match in name/description
    age: Age of the user
    income: Income of the user
    gender: Gender (male, female, other)
    employmentStatus: Employment status (unemployed, farmer, student, salaried, entrepreneur)
    disabilities: Disabilities (visual, hearing, mobility, intellectual, multiple, other)
    socialCategories: Social categories (SC, ST, OBC, EWS, GENERAL)
    maritalStatus: Marital status (single, married, divorced, widowed)
    religion: Religion
    state: State/UT name
    district: District name
    urbanRural: Area type (urban, rural)
    profession: Profession
    casteRequired: Whether caste certificate is required
    domicileRequired: Whether domicile certificate is required
    category: Program category
    benefitType: Type of benefit (cash, subsidy, scholarship, loan, insurance, pension, grant, in-kind)
    active: Whether to only include active schemes
    limit: Maximum number of results (default: 100)
    offset: Number of results to skip (default: 0)

ParametersJSON Schema

Name	Required	Description	Default
`q`	No
`age`	No
`income`	No
`gender`	No
`employmentStatus`	No
`disabilities`	No
`socialCategories`	No
`maritalStatus`	No
`religion`	No
`state`	No
`district`	No
`urbanRural`	No
`profession`	No
`casteRequired`	No
`domicileRequired`	No
`category`	No
`benefitType`	No
`active`	No
`limit`	No
`offset`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It lists many parameters but does not disclose behavioral traits like filtering logic (AND/OR), case sensitivity, default sorting, or performance considerations. It adequately describes input but lacks deeper behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose sentence, followed by a structured list of parameters. It is efficient but slightly long due to 20 entries; overall well-organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 20 parameters and no annotations, the description covers input but does not mention output schema, return format, or pagination behavior beyond limit/offset. An output schema exists but is not referenced, leaving some gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% (no descriptions in schema), so the description compensates by listing all 20 parameters with brief explanations (e.g., 'age: Age of the user'). However, these explanations are minimal and do not include constraints or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Search schemes by user profile/filters' with a specific verb and resource, and mentions eligibility matching, which distinguishes it from sibling tools like create, delete, read, update, and health.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not explicitly state when to use this tool versus alternatives, but the context of sibling tools (CRUD + health) implies this is the search/filter tool. No explicit when-not or alternative guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

update_schemeA

Update a government scheme record by ID. Pass only fields to change.

Args:
    id: The numeric ID of the scheme to update
    Other params: Same as in `create_scheme`; only provided values will be updated

ParametersJSON Schema

Name	Required	Description	Default
`id`	Yes
`code`	No
`name`	No
`description`	No
`department`	No
`category`	No
`benefit_type`	No
`benifit_details`	No
`terms_and_conditions`	No
`scheme_raw_text`	No
`official_website`	No
`application_link`	No
`url`	No
`contact`	No
`min_age`	No
`max_age`	No
`genders`	No
`income_min`	No
`income_max`	No
`employment_status`	No
`disabilities`	No
`social_categories`	No
`marital_statuses`	No
`religions`	No
`states`	No
`districts`	No
`urban_rural`	No
`professions`	No
`required_documents`	No
`caste_required`	No
`domicile_required`	No
`is_active`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses that only provided fields are updated (partial update behavior), which is a key behavioral trait. However, it does not mention what happens if the ID does not exist, error handling, authorization needs, or whether the update is destructive. The partial update detail is useful but leaves gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise: two sentences and a short args list. It is front-loaded with the purpose. The reference to create_scheme for other params is efficient, though it assumes the agent will look up that tool. No wasted words, but slightly under-specified for a tool with many parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (32 parameters, no schema descriptions, no annotations), the description is incomplete. It does not explain validation, required parameters beyond id, or the response format (though output schema exists). The reference to create_scheme helps but does not fully cover the semantics of all fields or edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It only explains the 'id' parameter and refers to create_scheme for others, without specifying the meaning of any field (e.g., 'code', 'name'). The schema titles provide some semantics, but the description adds minimal value. For 32 parameters, this is insufficient.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Update' and the resource 'government scheme record by ID'. It also adds the important constraint 'Pass only fields to change', distinguishing it from a full replacement. This makes the purpose specific and unambiguous, even without explicitly contrasting with sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies usage for updating an existing scheme rather than creating or deleting it. The phrase 'Pass only fields to change' provides guidance on how to use the tool. However, it does not explicitly state when not to use it (e.g., for creation use create_scheme) or list any prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

6 tool updatesv0.1.3Jun 17, 2026
- First observedcreate_scheme
- First observeddelete_scheme
- First observedhealth
- First observedread_scheme
- First observedsearch_schemes
- First observedupdate_scheme

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0

Disambiguation5/5

Each tool has a distinct purpose: CRUD operations (create, delete, read, update), search with filtering, and health check. No overlap or ambiguity.

Naming Consistency4/5

Tools follow a verb_noun pattern (e.g., create_scheme, delete_scheme), with 'health' as a simple noun. Minor inconsistency: 'search_schemes' uses plural but is still clear.

Tool Count5/5

Six tools is appropriate for a scheme management server: full CRUD plus search and health check. Not too many, not too few.

Completeness5/5

Covers all essential operations: create, read, update, delete, and search with eligibility criteria. Health check ensures connectivity. No obvious gaps for the domain.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

eligibility-mcp
io.github.quantumskils-arch
Deterministic eligibility checker for grants, jobs and scholarships in Africa.
Education & Learning Tools Research & Data
2
mcp-grantiq
io.github.bch1212
Search US grants + federal contracts (Grants.gov + SAM.gov) from any LLM.
Government Data Search
21
Federal Grants — find funding you are actually eligible for A
io.github.wyattpalm2-eng
Find US federal grants your organization is actually eligible to apply for. Free, no API key.
Government Data Open Data Research & Data
311
Grant Search A
xyz.krimskrams
Search U.S. federal grants and EU funding topics; monitor changes and download snapshots.
Government Data Open Data Search
51

Related MCP Servers

opportunity-mcp
Education & Learning Tools Search
revolutionarybukhari
A
license
A
quality
D
maintenance
Enables AI assistants to search and filter youth opportunities such as scholarships, fellowships, internships, conferences, and exchange programs, aggregated from multiple live sources.
Updated a day ago (2026-09-05 19:44 UTC)
6
1
MIT
Alumnx MCP Serverofficial
RAG Systems Search Government Data
alumnx-ai-labs
A
license
Not graded
quality
D
maintenance
Provides agricultural intelligence tools for pest/disease lookup, government scheme discovery, and SME knowledge retrieval via semantic search.
Updated 6 months ago (2026-03-03 13:00 UTC)
MIT
PlainGov-MCP
Government Data Documentation Access
fasterinnerlooper
A
license
B
quality
D
maintenance
Retrieves and explains government program information from official Canadian sources using a strict retrieval-first approach, with deterministic eligibility checks and full source attribution.
Updated 8 months ago (2026-01-11 22:26 UTC)
6
18
MIT
FarmSubsidy Korea MCP
Government Data Search
joseph-kang777
F
license
Not graded
quality
B
maintenance
Aggregates Korean agricultural subsidy announcements from multiple government sources. Enables searching, detailed viewing, and calendar integration for subsidy deadlines.
Updated 2 days ago (2026-09-04 22:46 UTC)
-

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/magicstack-llp/gov-scheme-mcp-py'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Government Scheme MCP Server

Features

Installation

From PyPI (when published)

From Source

Usage

As an MCP Server

Environment Variables

Available Tools

health()

create_scheme(...)

read_scheme(id)

update_scheme(id, ...)

delete_scheme(id)

search_schemes(...)

Configuration for MCP Clients

Claude Desktop

Other MCP Clients

Development

Setup

Testing

Code Formatting

Type Checking

API Requirements

License

Contributing

Support

Related Projects

Available Tools

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Alumnx MCP Serverofficial

Latest Blog Posts

MCP directory API

`health()`

`create_scheme(...)`

`read_scheme(id)`

`update_scheme(id, ...)`

`delete_scheme(id)`

`search_schemes(...)`