@munispot/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUNISPOT_API_KEY | Yes | Your MuniSpot API key (e.g., ms_live_your_key_here). Required for authentication. |
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 |
|---|---|
| search_municipalitiesB | Search and filter 20,000+ US municipalities by name, state, sector, MuniScore range, and population. |
| get_municipalityB | Get detailed profile for a single municipality by EIN. |
| get_financialsB | Get detailed financial line items from ACFR statements. Pro/Enterprise tier only. |
| get_scores_historyA | Get MuniScore history across all available fiscal years for a municipality. |
| compare_municipalitiesB | Compare 2-10 municipalities side by side for a given fiscal year. |
| get_economyB | Get economic and demographic data by municipality EIN, CBSA code, or state FIPS code. |
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 6 tools
Each tool targets a clear sub-resource: search (by name/filter), get_municipality (by EIN), compare (multi-entity), plus three data-domain getters (economy, financials, score history). The only soft overlap is that get_municipality's 'detailed profile' could plausibly subsume get_economy or get_scores_history, but the other descriptions are specific enough to steer selection.
All six tools follow a consistent snake_case verb_noun pattern (get_*, search_*, compare_*), with nouns that clearly identify the resource being fetched. No mixed conventions or vague verbs.
Six tools is a tight, well-scoped surface for a municipal-data API: one discovery tool, one entity lookup, one comparison, and three domain-specific data getters. Nothing looks redundant or padded.
The read-oriented surface covers discovery, single-entity detail, comparison, financials, economic/demographic data, and score trends across fiscal years, which handles most analytics workflows. Minor gaps exist: no way to enumerate available sectors/fiscal years or score components, and no bulk export, but agents can work around these.