grants-discovery-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| grants_search_opportunitiesA | Search US federal funding opportunities on Grants.gov. Returns one page of matches with ID, number, agency, open/close dates, and status. If more results exist, the result gives next_offset; call again with that offset. Use grants_get_opportunity with an ID for the full announcement (award sizes, eligibility, contacts). Filter values are codes: agencies like 'HHS-NIH11' (prefix match, e.g. 'HHS'), eligibilities like '25' (use grants_list_filter_options for codes). Examples:
|
| grants_get_opportunityA | Get the full announcement for one Grants.gov opportunity: summary, eligibility, award ceiling/floor, total funding, expected number of awards, cost sharing, key dates, and agency contact. Use grants_search_opportunities first to find the numeric opportunity ID. |
| grants_list_filter_optionsA | List valid filter codes for grants_search_opportunities: applicant eligibility codes, funding categories, and funding instruments, with how many current opportunities each matches. Call this when a user describes an applicant type (e.g. 'nonprofit', 'tribal government') or topic area and you need the matching code. |
| grants_search_past_awardsA | Search historical federal grant awards on USAspending.gov to see who has been funded, by whom, and how much. Useful for competitive research: find peer organizations funded for a topic, typical award sizes, and which agencies fund an area. Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a clearly distinct function: filter-code reference, opportunity search, single-opportunity detail, and historical award search. The descriptions explicitly state how the tools relate (use list_filter_options for codes, use search first to get an ID for get_opportunity), leaving no realistic ambiguity.
All four tools use the same grants_ prefix followed by a consistent verb_noun pattern (list_filter_options, search_opportunities, get_opportunity, search_past_awards). The naming is predictable and readable.
Four tools is a tight, well-scoped set for a grants discovery server, and each one earns its place (code lookup, search, detail, historical research). No redundancy or filler.
The read-only discovery lifecycle is well covered: filtering codes, paginated search, full announcement detail, and historical awards data. Minor gaps exist—no direct agency/organization lookup or saved-search/tracking capability—but these are workable within the stated discovery purpose.