Data Collection

santafeminutes.space

MCP server for searching and retrieving City of Santa Fe meeting information, including documents, agendas, transcripts, and related metadata.

1 endpoint6 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://santafeminutes.space/mcp

No auth detected

MCP server metadata

Name: santa-fe-minutes
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Santa Fe Minutes is the public archive of City of Santa Fe, New Mexico government meetings. This server covers Santa Fe only. Search before answering. Use transcripts for what occurred in the meeting. Use agendas for procedural stage (introduced, postponed, recommended, approved, failed). Use attachments for substantive detail such as the text of an ordinance, a staff report, or a site plan. Return the canonical Santa Fe Minutes URL with every claim. Preserve body, action, procedural stage, and finality. A committee or board recommendation is that body's action. It is not action by the Governing Body, and it is not "Santa Fe approved" something, unless the record shows the Governing Body took that final action. These tools return snippets and metadata. They do not return full transcripts or PDF bodies. Follow the URLs for the complete public record.

Known tools 6

search

Search City of Santa Fe meetings, documents, and transcripts.

Inferred read-only

list_meetings

List City of Santa Fe meetings in a date range of at most 366 days, optionally for one body such as Governing Body or Planning Commission.

Inferred read-only

get_meeting

Agenda, files, and attachment URLs for one meeting id.

Inferred read-only

get_document

Metadata and a capped text extract for one agenda attachment id, plus the canonical document URL.

Inferred read-only

get_transcript

Executive summary, decisions, motions, and topics for one meeting, plus the transcript URL.

Inferred read-only

get_item

One agenda item on a meeting, with attachment URLs, short text excerpts, and transcript snippets for that item title.

Inferred read-only

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.santa-fe-minutes]
url = "https://santafeminutes.space/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "santa-fe-minutes": {
      "type": "http",
      "url": "https://santafeminutes.space/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: santa-fe-minutes
Remote MCP URL: https://santafeminutes.space/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": {
    "santa-fe-minutes": {
      "url": "https://santafeminutes.space/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "santa-fe-minutes": {
      "type": "http",
      "url": "https://santafeminutes.space/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "santa-fe-minutes",
  "transport": "streamable-http",
  "url": "https://santafeminutes.space/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.