San Joaquin County GIS — San Joaquin County, California open geospatial data (ArcGIS).
MCP servers
Compare source listings, connection options and authentication requirements.
Showing 12,361–12,384 of 165,917 resultsPage 516 of 6,914
Candidate groups, not verified unique MCPs. How grouping works
City of San Jose GIS — San Jose, California open geospatial data (ArcGIS).
San Juan County GIS — San Juan County, New Mexico open geospatial data (ArcGIS).
City of Sarasota GIS — Sarasota, Florida open geospatial data (ArcGIS).
Sarpy County GIS — Sarpy County, Nebraska open geospatial data (ArcGIS).
City of Seattle GIS — Seattle, Washington open geospatial data (ArcGIS).
City of South Bend GIS — South Bend, Indiana open geospatial data (ArcGIS).
Stanislaus County GIS — Stanislaus County, California open geospatial data (ArcGIS).
St. Louis County GIS — St. Louis County, Missouri open geospatial data (ArcGIS).
City of Sumter GIS — Sumter, South Carolina open geospatial data (ArcGIS).
Tallahassee-Leon County GIS — Tallahassee-Leon County, Florida open geospatial data (ArcGIS).
City of Tampa GIS — Tampa, Florida open geospatial data (ArcGIS).
City of Tempe GIS — Tempe, Arizona open geospatial data (ArcGIS).
City of Tigard GIS — Tigard, Oregon open geospatial data (ArcGIS).
City of Toledo GIS — Toledo, Ohio open geospatial data (ArcGIS).
City of Tucson GIS — Tucson, Arizona open geospatial data (ArcGIS).
City of Tulsa GIS — Tulsa, Oklahoma open geospatial data (ArcGIS).
City of Victoria GIS — Victoria, BC (Canada) open geospatial data (ArcGIS).
Vilas County GIS — Vilas County, Wisconsin open geospatial data (ArcGIS).
Washington County GIS — Washington County, Minnesota open geospatial data (ArcGIS).
City of Yakima GIS — Yakima, Washington open geospatial data (ArcGIS).
Search and update ARCH-Insight: architecture fact sheets, applications, tickets, tasks, incidents.
Universal Language briefings, FusionGirl context JSONs, service catalog, agent info. x402-enabled.
Sign in with your Archbee account through OAuth. Claude connects to the Archbee team you have open when you sign in, and can only reach doc spaces owned by that team. A team admin approves the connection.
What this catalog covers
- Source listings
- 167,897
- Candidate groups
- 168,273
- Setup-eligible endpoints
- 30,743
Sources observed 2026-10-24–2026-11-12. Listings can overlap across sources. Groups are identity candidates; setup eligibility is not a successful connection test.
SourcesMCP data from Glama connectorsMCP data from Glama source codeOfficial MCP RegistryClaude connector directoryAPI Tracker · publisher documentationSlack MCP directory
Default browsing excludes 2,356 specialized utility groups across the catalog. They remain available through keyword search and direct links. This editorial filter does not change the indexed totals or establish publisher quality.
Categories currently cover records matched to our reviewed catalog; other listings remain Uncategorized. Source-only projects have no generated connection option. Browse reviewed official MCPs →
- Glama connectors
API result set; pagination may cap at approximately 1,000 connectors. Not exhaustive.
- Glama source code
Complete chronological source-code catalog response; includes source-reported author classifications, not publisher attestations or ready-to-use endpoints.
- Official MCP Registry
Complete paginated registry response; registry membership is not publisher verification.
- Claude connector directory
Complete public Claude directory MCP components. Source tiers, tools, icons and sign-in hints are declarations, not publisher or runtime verification.
- API Tracker · publisher documentation
Reviewed publisher and third-party remote, local and setup-only MCP listings. Publisher status is retained per exact connection. Discoverability does not establish connection readiness.
- Slack MCP directory
Reviewed additions discovered through the public Slack Marketplace MCP category. Complete discovery inventory is retained separately; membership does not prove external-client compatibility.
Listings are grouped by exact public endpoints, exact package sets, or explicit reviewed identity bindings. Shared names or repositories alone do not merge implementations. Official includes publisher evidence and accepted source author classifications. It does not mean independently verified, runtime-tested or security-certified.