Maryland Community Compass MCP server — tools & history

Maryland Community Compass MCP server: observed open status, tool schemas, linked apps and version history.

Maryland Community Compass

Endpoint: https://compass.maryland.gov/mcp

Observed status: open. Checked: 2026-10-11T06:23:43+00:00.

Linked apps

• Maryland Community Compass

  Maryland's neighborhood development data platform.

Observed tools

• geocode_address — Geocode a street address to WGS84 coordinates. Expected address format: "<street number and name>, <city or town>, <two-letter state abbreviation> [<ZIP>]" - The two-letter state abbreviation goes at the tail, uppercase. - County names in the state slot ('Baltimore, Baltimore County, MD') are not required and reduce match quality; city and state alone match better. Coverage: this tool resolves Maryland addresses only. Resolution runs the SDAT parcel index first (exact prefix, then trigram fuzzy), then falls back to Maryland's iMap geocoder. Addresses outside Maryland may resolve to a similarly-named Maryland location instead of returning an error — check the response `confidence` and `warning` fields before chaining the coordinate into other tools. Response fields: - `address`, `latitude`, `longitude`, `county` - `source`: 'sdat' | 'imap' - `match_type`: 'prefix' | 'trigram' | 'imap' - `confidence`: 'high' | 'medium' | 'low' (only exact-prefix matches earn high) - `warning`: null on high-confidence Maryland matches; a short string otherwise (fuzzy match, non-MD state token in the input, etc.) - `score`, `score_source`: raw similarity signal for fuzzy matches (trigram 0.0-1.0, iMap 0-100)
• get_program_details — Fetch full details for one funding program by slug: eligibility, application process, deadlines, contact info, source URLs, requirements.
• get_statistics — Program-count breakdown across one categorical facet. `group_by` is one of: agency, assistance_type, county, industry, eligible_org_type, funding_source, business_stage, data_quality. `top_n=0` returns all groups sorted by count desc; positive N truncates to the top N.
• list_community_plans — Return the Maryland comprehensive / community plans covering the given lat/lng. Exact-overlap plans come first ({plan_slug, title, jurisdiction, year}); if none contains the point, returns the 3 nearest plans within 3 miles with distance in miles.
• list_filter_options — Enumerate valid filter values for the funding-program facets: agencies, assistance types, counties, industries, org types, funding sources, business stages, incentive-area names. Pass `fields` to restrict to a subset; omit to get all facets.
• list_zoning_jurisdictions — List every Maryland jurisdiction whose zoning ordinance is loaded. Returns [{jurisdiction_slug, jurisdiction_type, platform}]. `platform` values, from most-structured to least: `open_law`, `ecode360`, `municode`, `american_legal`, `municipalcodeonline`, `encodeplus` (all structured code — sections match the code's own numbering), and `generic` (scraped web pages with heterogeneous chapter-level scope). Slug format: '{county-name}-county' for counties, '{city-name}' or 'baltimore-city' for municipalities.
• list_zoning_sections — List every section of one jurisdiction's zoning ordinance. Each entry has section_id, section_title, character count, and source URL. Ordered as the code itself is ordered (article / chapter / section).
• lookup_environmental — Return MDE Land Restoration Program sites (Brownfields, VCP, NPL, Site Assessment, Federal Facility) and MDE determination areas (critical area, chesapeake bay tidal buffer, wetlands) within radius_miles of the given point. Default radius is 0.5 miles.
• lookup_historic — Return historic-register entries from the Maryland Historical Trust (National Register of Historic Places, Maryland Inventory of Historic Properties, Determinations of Eligibility, preservation easements) within radius_miles of the given point. Each entry is classified as 'contains_site', 'intersects', or 'nearby' relative to the reference geometry. Default radius 0.5 miles.
• lookup_natural_resources — Return Maryland DNR Conservation Easements and Green Infrastructure areas within radius_miles of the given point. Default radius 0.25 miles.
• lookup_neighborhood_indicators — Return census-tract-level neighborhood indicators for the point (demographics, housing, economic growth, development activity) with county and state medians for comparison. Pass an optional `metrics` list to filter to specific keys; otherwise a default subset is returned.
• lookup_parcel — Look up SDAT (State Department of Assessments and Taxation) parcel data at a lat/lng. Returns parcel attributes: SDAT id, zoning code, acreage, assessed values, construction quality, sale history, utility service. Raw codes are translated to semantic names with human-readable descriptions.
• lookup_vacancy_notices — Return active Baltimore City Vacant Building Notice (VBN) records on or near the given point. BC-only — points outside Baltimore City return `applicable: false` with a note. Default radius 0.1 miles.
• lookup_zoning_and_context — Return the parcel's zoning classification, any Maryland state or local incentive-area overlays it falls inside (Enterprise Zone, Opportunity Zone, LIHTC QCT/DDA, Sustainable Community, Transit-Oriented Development, and others), and titles of overlapping community plans.
• read_community_plan — Return the markdown body of one comprehensive plan by plan_slug. Without `max_chars`, returns up to 120 KB and paginates the rest via `truncated: true` + `next_offset`. Response carries an absolute `pdf_url` for citation. Use `offset` + `max_chars` to fetch a narrow window.
• read_zoning_section — Return the markdown body of one ordinance section by section_id. Without `max_chars`, returns up to 60 KB (the section-body cap); larger sections paginate via `truncated: true` + `next_offset`. Use `offset` + `max_chars` to fetch a narrow window.
• recommend_programs — Recommend funding programs by scoring against a structured profile of the user (org_type, county, industry, business_stage, demographics, need) rather than by keyword. Pass any subset of profile fields; each contributes to a composite score. Hard filters: is_accepting (default true), include_closed (default false), min_quality (default 'medium'). Programs with zero profile matches are excluded.
• search_community_plan_text — Postgres full-text search across one plan's chunk index by plan_slug. Each hit returns a match `offset` + `length` + a short snippet. Query supports websearch syntax. Default limit 8.
• search_funding — Full-text and faceted search over Maryland state and local government incentive programs (grants, loans, tax credits, training, technical assistance). Common Maryland agency acronyms auto-expand in both the free-text `query` and the `agency` filter (e.g. 'DHCD' matches 'Department of Housing and Community Development'). Filters are AND across fields, OR within a field, resolved case-insensitively (e.g., 'anne arundel' → 'Anne Arundel County'). Ambiguous filter values return an error listing the candidates; unknown filter values return an error with a pointer to list_filter_options.
• search_zoning_text — Postgres full-text search across one jurisdiction's ordinance sections. Each hit returns section metadata, a short snippet, and the match `offset` + `length` within the section. Query supports websearch syntax (e.g. "C-2 use table", "parking minimum -waiver"). Ranks by relevance across subsection_title (weight A) and content (weight B). Pass `distinct=True` to collapse duplicate hits from the same parent section. Default limit 10. Zone codes: hyphenation variants (`RSF-95`, `RSF95`, and the Unicode-hyphen `RSF‐95`) are normalized to hit the same content — no need to guess which form the ordinance uses. Bare-code queries (e.g. `RSF-95` on its own) tend to surface use tables and dimensional standards that co-locate the zone code with heading text but not the words `permitted uses` or `dimensional requirements`, so a bare-code query alongside topic-narrowed queries is often more comprehensive than either alone.

Data as of 2026-10-11T06:23:43+00:00.

OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.

REST API specification · Guide for AI clients · Manage API keys and MCP connections