Saltar al contenido
Logo de OpenPublica

Servidor MCP de OpenPublica

Qué servidores del registro oficial de MCP son de OpenPublica, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-18

← Volver a OpenPublica

De quién es el servidor
  • Nombre en el registrocom.openpublica/civic-meetingsverificado en el registro MCP

El nombre en el registro está bajo openpublica.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-18
  • Estadorespondecomprobado el 2026-10-18
  • Herramientas16
  • El servidor se llamaOpenPublica
  • Versión del servidor2.0.0
  • Versión del protocolo2025-06-18

El 2026-10-18 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 117 ms.

Medido cada díacomprobaciones diarias: 2, la primera el 2026-10-19
  • Respondiómidiendo2 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta1746 ms
  • Espacio en el contexto del agente≈ 4279 tokenslas definiciones de todas sus herramientas (16), que el agente lleva en cada turno
  • Definiciones de herramientasA · 99 de 100
  • Parámetros sin descripción: en 1 de 16

Conviene revisar

Ninguna de las cinco señales de alerta en estas definiciones.

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece16 herramientas · leído el 2026-10-18
  • search_meeting_content

    Search public meetings once across metadata and stored transcript text. Returns one card per meeting and native pagination metadata, without a total. Small current-text previews can be absent and do not establish timestamps. Text…

  • search_meetings_semantic

    Find AI summaries by meaning; use search_meeting_content for stored words. Results carry relevance_score and a summary preview. Narrow with government, category_tag, topic or dates; get_meeting retrieves the full summary.

  • list_recent_meetings

    Browse meetings newest-first, optionally filtered by government, type, topic, or date. Use this for "what are the most recent meetings" or to page through a government's history. For topical questions, prefer `search_meetings_semantic`.

  • get_meeting

    Get a single meeting's full AI summary and topics. Set `include_transcript=true` to also retrieve the complete transcript text for direct quotation. Returns an error object if the meeting is not found.

  • search_meeting_transcript

    Use unified stored-text search inside one currently public meeting. Returns an optional current-text preview, without resolving timing. A text match can lack a literal preview; use get_meeting(include_transcript=true) for full source…

  • find_local_governments

    Discover which governments OpenPublica tracks near a coordinate. Returns nearby governments with their `account_id`, which you can pass to the other tools to scope results to a specific city or board. Note OpenPublica only covers a…

  • find_governments_by_name

    Resolve a place *name* to the governments OpenPublica tracks there. Use this when you know a city/state name but not its coordinates — it returns matching governments with their `account_id` (prefix matches first), which you then pass to…

  • find_governments_by_zip

    Resolve a ZIP code to nearby tracked governments. Convenience wrapper: geocodes the ZIP, then finds the governments OpenPublica tracks nearest that point. Returns their `account_id`s plus the resolved location. An empty `governments` list…

  • get_government_info

    Get a tracked government's profile: name, location, and meeting categories.

  • get_government_stats

    Get meeting-activity stats for a government over a recent window. Returns total meeting count, a per-day activity map, and a breakdown of meeting categories — useful for "how active has X been lately?" questions.

  • discover_meeting_vocabulary

    Discover the valid category and topic filter values before filtering a search. Meeting `category_tag`s are opaque UUIDs and topics have no fixed list, so you cannot guess them. Call this first to get the real values, then pass a returned…

  • list_government_documents

    List a government's adopted plan and budget documents. Each entry carries `covers` — every general-plan element that document answers for. A city that publishes one bound general plan satisfies all eight with the same PDF, so do not…

  • get_document

    One document's metadata. Use read_document_pages to read it. If an `availability` key is present, read it before quoting figures: its `problems` are transcription-lint findings, most often a footnote marker that may have been merged into…

  • read_document_pages

    Read a page range of a document as markdown. Pages are transcribed from rendered pixels, so tables and scanned text come through as text. A page that could not be transcribed appears as a marked hole rather than being silently dropped…

  • search_documents

    Search adopted plan and budget documents, returning page-cited excerpts. Each hit's `text` is a short passage around the match, not the full page — call read_document_pages with the hit's `first_page` to read it in context. Every hit…

  • get_coverage_overview

    Get estimated stored-record totals, not publication-filtered coverage. Counts do not establish completeness, searchability or freshness. DC is reported separately from states as `includes_dc`.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "civic-meetings": {
      "type": "http",
      "url": "https://api.openpublica.com/mcp"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.