mcpField
A
AICD API

AICD API

Remote
aicdapi.comLegal & Government0Updated 3w ago

About AICD API

AICD API provides source-linked records of Dallas–Fort Worth local-government activity for AI agents and developers. Its REST API and remote MCP server cover classified agenda items, meeting cadence, and source health.

Key features

  1. 01Ranked civic agenda search
  2. 02Agenda item lookup by ID
  3. 03Coverage and source-health checks
  4. 04Missing-record reporting and status
  5. 05Links to original public sources

Use cases

  1. 01Find Dallas zoning agenda items
  2. 02Review a specific government agenda record
  3. 03Check coverage gaps and source health

MCP support

AICD API offers a remote MCP server over Streamable HTTP. It exposes tools to search and retrieve agenda records, inspect coverage, and report or check missing data.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://aicdapi.com/api/v1/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://aicdapi.com/api/v1/mcpAuth required

Tools

Details

From the project README

AICD API — civic records API and MCP server for AI agents

AICD API gives AI agents and developers source-linked local-government records for Dallas-Fort Worth, Texas: classified city council and commissioners court agenda items, meeting cadence, and per-source health. Every result links back to the public government page it came from. It is available as a REST API and as a remote MCP server.

MCP endpoint

https://aicdapi.com/api/v1/mcp

Streamable HTTP transport, authenticated with Authorization: Bearer <AICD API key>. Follow the setup guide at https://aicdapi.com/help/mcp-setup for client configuration.

REST quickstart

No key needed for the public routes:

# Recent classified Dallas zoning agenda hits, each with meetingAt and sourceUrl
curl --fail --silent --show-error \
  'https://aicdapi.com/api/v1/public/agenda-hits?jurisdictionSlug=dallas&topicSlug=zoning'

# Dated DFW coverage catalog and known gaps
curl --fail --silent --show-error \
  'https://aicdapi.com/api/v1/public/coverage?limit=10'

With an API key (create one at https://aicdapi.com/account; see https://aicdapi.com/help/api-keys):

curl --fail --silent --show-error \
  --header "Authorization: Bearer $AICD_API_KEY" \
  https://aicdapi.com/api/v1/data/health

This repository

This repository also holds the MCP discovery record for AICD API.

  • server.json — the record for the remote MCP server, following the official MCP Registry server.json schema (revision 2025-12-11). Registry name: com.aicdapi/records.

The record is served by AICD API at https://aicdapi.com/server.json, with a byte-identical, non-normative convenience alias at https://aicdapi.com/.well-known/mcp.json; the alias path is not part of any adopted MCP discovery standard. It is published in the Official MCP Registry — entry: https://registry.modelcontextprotocol.io/v0.1/servers/com.aicdapi%2Frecords/versions/1.0.0

Connection

Tools

ToolPurpose
search_agendaFind ranked civic agenda records
get_agenda_itemRead one agenda record by id
get_coverageCheck supported source health
report_missing_dataReport a missing public record
get_data_reportRead a missing-data report status

Coverage

Dallas-Fort Worth is the first coverage area; broader Texas coverage is planned. Every result stays linked to the public source it came from, and source health is reported per source. An empty result does not prove there was no government activity.

Sources

Contact

[email protected]

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.