GrantSonar
Server Details
Search verified-open US grants (federal, state, foundation). Read-only MCP for AI agents.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 7 of 7 tools scored.
Each tool targets a distinct action: dismissing/restoring, fetching details, viewing individual applications, listing all applications, listing matches, saving/setting pipeline status, and searching. No two tools overlap in purpose.
All tools follow a consistent verb_noun pattern in snake_case, e.g., dismiss_grant, get_grant, search_grants. The naming is predictable and uniform.
With 7 tools covering search, detail retrieval, pipeline management, and application tracking, the count is appropriate for the domain. Slightly fewer than a full-featured system, but still well-scoped.
Core grant discovery and pipeline management are covered, but missing operations like creating an application, updating application drafts, or permanently removing pipeline entries. The surface is functional but has notable gaps.
Available Tools
9 toolsdismiss_grantDestructiveInspect
Dismiss a grant from YOUR active feed, or restore it (dismissed=false). Reversible. Requires your API key.
| Name | Required | Description | Default |
|---|---|---|---|
| grant_id | Yes | Grant UUID. | |
| dismissed | No | true = dismiss (default), false = restore. |
draft_application_sectionDestructiveInspect
Generate an AI first-draft for one section of YOUR application, grounded in the funding notice and your org profile, and save it into that section (prior content snapshotted first). Requires a paid API key. This is the only tool that runs the grant writer, so it is metered heavily. Returns the drafted text. Use get_my_application for section_keys.
| Name | Required | Description | Default |
|---|---|---|---|
| section_key | Yes | Which section to draft (see get_my_application). | |
| document_type | No | Draft a short Letter of Inquiry ("loi") or a full section ("full"). Defaults to the application's submission stage. | |
| application_id | Yes | Application UUID. |
get_grantRead-onlyInspect
Fetch the full detail of a single grant opportunity by its GrantSonar grant_id (UUID), including synopsis, eligibility, deadlines, and award amounts.
| Name | Required | Description | Default |
|---|---|---|---|
| grant_id | Yes | GrantSonar grant UUID (from a search_grants result). |
get_my_applicationRead-onlyInspect
Fetch one of YOUR grant applications (status + every section draft) by application_id or grant_id. Requires your API key.
| Name | Required | Description | Default |
|---|---|---|---|
| grant_id | No | Grant UUID — resolves your application for that grant. | |
| application_id | No | Application UUID. |
list_my_applicationsRead-onlyInspect
List YOUR organization's grant applications (id, grant title, status, document type, last updated). Requires your API key.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_my_matchesRead-onlyInspect
List YOUR organization's scored grant matches — the same personalized matches shown on your GrantSonar dashboard. Requires your API key. Returns match tier, score, reasons, pipeline status, and a URL per grant.
| Name | Required | Description | Default |
|---|---|---|---|
| tier | No | Optional: only return matches in this tier. | |
| view | No | Which list (default "matches" = your active personalized feed). | |
| limit | No | Max results (default 25). |
save_grantInspect
Save a grant to YOUR pipeline, or set its status to pursuing/applied. Reversible. Requires your API key. Mirrors the dashboard Save button.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Pipeline status (default "saved"). | |
| grant_id | Yes | Grant UUID (from list_my_matches or search_grants). |
search_grantsRead-onlyInspect
Search open grant opportunities in the GrantSonar corpus (federal, state, and foundation grants). Uses semantic similarity over a plain-English description of the project or need, with a keyword fallback. Returns title, agency, deadline, award amounts, similarity score, and a GrantSonar URL per hit.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results (1-25, default 10). | |
| query | Yes | Plain-English description of the project, organization, or funding need (e.g. "after-school STEM programs for rural Missouri students"). |
update_application_sectionDestructiveInspect
Write content into one section of YOUR grant application (replace or append). Requires your API key. The prior draft is snapshotted to version history first, so this is recoverable. Use get_my_application to see section_keys.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | replace (default) overwrites; append adds to the end. | |
| content | Yes | The text/HTML to write into the section. | |
| section_key | Yes | Which section to write (e.g. "statement_of_need"). See get_my_application. | |
| application_id | Yes | Application UUID (from list_my_applications). |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!