edp-mcp
OfficialRelated Servers
Alternatives to edp-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides access to Urban Institute's Education Data API through Claude, enabling users to query and analyze detailed educational data from schools, districts, and universities.22MIT
- AlicenseNot gradedqualityBmaintenanceEnables natural-language queries about US K-12 public schools, districts, per-pupil funding and spending, and child poverty estimates from keyless federal data.359 npmMIT

ew-mcpofficial
AlicenseAqualityCmaintenanceEnables querying of a locally pinned snapshot of the Education-to-Workforce Indicator Framework — 99 indicators and 11.8M observations — to browse questions, describe metrics, resolve places, and fetch or rank data across national, state, county, and district levels.4MIT- AlicenseBqualityBmaintenanceEnables discovery and summarization of French education data, including school directories, geocoded establishments, IPS, Parcoursup, and exam datasets.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and querying Utah Open Data datasets via the Socrata SoQL API, including datasets, metadata, and row-level data retrieval.8 npmMIT
- AlicenseNot gradedqualityCmaintenanceFederated MCP server that routes K-12 education data requests to public sources like Urban Institute, EDC/Zelma, NAEP, and MA E2C, handling comparability and provenance automatically.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: discover datasets, inspect schema, fetch raw rows, aggregate, decode codes, and resolve names to IDs. The potentially confusing get_data/get_summary pair is explicitly separated and cross-referenced.
All tool names follow a consistent snake_case verb_noun convention: describe_dataset, search_datasets, get_data, get_summary, lookup_codes, resolve_entity. No mixed casing or vague generic verbs appear.
Six tools form a compact, non-redundant set that covers the read-only data-portal workflow well. Each tool earns its place, and the count is well within the ideal range for an agent to navigate comfortably.
The tool surface covers the full query lifecycle: find datasets, inspect variables and filter fields, resolve codes and entity names, fetch raw data, and aggregate server-side. Known unsupported operations are explicitly documented with workarounds, leaving no obvious dead ends.