SummitFlow MCP
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| federal_holidaysA | List US federal holidays for a year, with observed dates. Observed dates matter more than actual ones for deadlines: a holiday on a Saturday closes offices the Friday before. |
| business_days_betweenA | Count business days between two dates, skipping weekends and US federal holidays. Dates are ISO format (YYYY-MM-DD). |
| add_business_daysA | Add (or subtract, with a negative number) business days to a date, skipping weekends and US federal holidays. |
| grant_deadline_planA | Work backward from a funder deadline to the dates that actually matter. A deadline is not a plan. This returns when to start drafting, when the internal review copy is due, and when the packet must be complete, using realistic lead times with weekends and federal holidays handled. application_type: loi | proposal_new | proposal_renewal | federal | report |
| grant_budgetA | Build a grant budget with fringe and indirect calculated on the correct base. indirect_base: 'mtdc' (Modified Total Direct Cost) or 'tdc' (Total Direct Cost). MTDC is the common federal base and it EXCLUDES equipment and the portion of each subaward/contract above the first $25,000. Applying your rate to total direct costs instead is the single most common budget error, and it inflates the ask in a way reviewers notice. |
| volunteer_time_valueA | Value volunteer time for match requirements or an annual report. Defaults to the published national rate. Skilled volunteers doing professional work (legal, accounting, medical) should be valued at the rate for that work instead, which most funders accept if you document it. |
| in_kind_valueB | Total donated goods and services. Each item needs 'description' and 'fair_market_value'; optional 'quantity' (default 1). |
| grant_lead_timesC | The lead times behind grant_deadline_plan, with the reasoning for each. |
| summitflow_resourcesC | Free grant templates, guides and calculators on the web. |
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 9 tools
Each tool has a clearly distinct purpose: date calculations (federal_holidays, business_days_between, add_business_days), planning (grant_deadline_plan), budgeting (grant_budget), valuation (volunteer_time_value, in_kind_value), reference (grant_lead_times, summitflow_resources). Even the date-related tools are complementary: listing holidays, counting business days, and adding business days serve different needs. No two tools appear to do the same thing.
All tool names follow a consistent lowercase-with-underscores style and are descriptive. However, the grammatical pattern is not uniform: some are verb phrases (add_business_days) while others are noun phrases (business_days_between, volunteer_time_value). This minor inconsistency keeps it from a 5, but the overall naming is predictable and readable.
With 9 tools, the server is well-scoped for its purpose. Each tool addresses a distinct aspect of grant planning—deadlines, budgets, match valuation, and reference materials—without unnecessary redundancy. This is within the ideal 3-15 range and feels comprehensive without being bloated.
The core grant planning workflow is well covered: date calculations, deadline planning, budget construction, and volunteer/in-kind valuation. A possible gap is the lack of tools for more advanced grant management tasks like tracking submitted applications or generating budget narratives, but the existing tools form a coherent set for the stated purpose. The inclusion of a resources tool helps round out the surface.