INDIVIDUAL MCP TOOL

list_datasets

Enumerate every approved Georgia dataset (topic) and the shared dimensions.

georgiacivicdata.orgnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.georgiacivicdata.org/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_datasets and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

georgiacivicdata.org

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.georgia-public-data]
url = "https://mcp.georgiacivicdata.org/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "georgia-public-data": {
      "type": "http",
      "url": "https://mcp.georgiacivicdata.org/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: georgia-public-data
Remote MCP URL: https://mcp.georgiacivicdata.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "georgia-public-data": {
      "url": "https://mcp.georgiacivicdata.org/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "georgia-public-data": {
      "type": "http",
      "url": "https://mcp.georgiacivicdata.org/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "georgia-public-data",
  "transport": "streamable-http",
  "url": "https://mcp.georgiacivicdata.org/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search_datasets — Keyword search over the catalog metadata (topic names, descriptions, tags, AND column names/descriptions) — the discovery entry point when you don't know the exact topic name.
describe_dataset — Full schema for one topic: every column (name/type/role/unit/value range/null-meaning), the exact `filters` list with enum values (read this before query_dataset — it is the authoritative set of filter keys), the FK→dimension join shape (`foreign_keys`), example queries, usage, limitations, null semantics, tags, and `schema_hash` (for cache/drift detection).
query_dataset — Query one topic's gold facts with dimension labels joined in (the district/school/county/demographic names come back on every row).
distinct_values — List the distinct values of ONE filterable column of a topic — the fast way to learn valid filter values before query_dataset, especially for FREE categoricals and FK codes (district_code/school_code/county_fips/demographic) that carry no enum in describe_dataset (a wrong guess otherwise returns an empty page with no error).
aggregate — Compute a grouped aggregate over one topic — the aggregation-first path.
resolve_entity — Resolve a place or demographic NAME or CODE to its stable keys + labels — the right way to turn 'Atlanta Public Schools' / 'Fulton' / a raw code into the district_code / school_code / county_fips / demographic to filter by (a wrong code guess otherwise returns an empty query_dataset page).
describe_dimension — Schema for one dimension (districts / schools / counties / demographics): the (possibly composite) primary key, the attribute columns a join attaches, the cross-dataset `link_keys` (e.
get_dimension — Paginated read of a dimension table — the label lookups (district names, school names, county names, demographic labels).