Saltar al contenido
Logo de Meta Council

Servidor MCP de Meta Council

Qué servidores MCP son de Meta Council, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-24

← Volver a Meta Council

De quién es el servidor
  • Nombre en el registrocom.meta-council/decision-intelligenceverificado en el registro MCP

El nombre en el registro está bajo meta-council.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-24
  • Estadorespondecomprobado el 2026-10-24
  • Herramientas280
  • El servidor se llamameta-council
  • Versión del servidor2.12.0
  • Versión del protocolo2025-06-18

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

¿Debe un agente conectarlo?Aún no está claro
  • Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
  • Comprobado 3 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • Para "Pressure-test a strategic decision with several AI expert views", la primera llamada probable es run_council.
  • create_outreach_campaign, add_outreach_lead, create_outreach_pitch, create_deal, update_deal cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Sus definiciones ocupan unos 69999 tokens de contexto: activa solo las herramientas que necesita la tarea.
  • Parámetros sin tipo o sin descripción en 196 de 280 herramientas: revisa los argumentos antes de llamar.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 3, la primera el 2026-10-24
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 3 hasta ahora
  • Respondiómidiendo3 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta273 ms
  • Espacio en el contexto del agente≈ 69.999 tokenslas definiciones de todas sus herramientas (280), que el agente lleva en cada turno
  • Definiciones de herramientasB · 88 de 100
  • Resultados tipados13 de 280 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin descripción: en 196 de 280

Qué puede hacer un agente con él

  • no está claro · Compare acquisition offers and their risks before deciding
  • puede · Pressure-test a strategic decision with several AI expert views
  • no está claro · Run multi-step due diligence or incident postmortem workflows

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: create_outreach_campaign, add_outreach_lead, create_outreach_pitch, create_deal, update_deal

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. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece280 herramientas · leído el 2026-10-24
  • run_council

    Submit a question or decision to Meta Council. A panel of specialized AI agents will independently analyze it, then a synthesis step combines their opinions into a unified recommendation with full transparency. Starts asynchronously by…

  • plan_council

    Resolve the effective Council models, parameters, tools, and setup reasons for this account without starting a session, calling a provider, or recording usage.

  • list_panels

    List all available expert panels with their descriptions and agent counts.

  • list_agents

    List all available expert agents with their roles, domains, and specialties.

  • get_session

    Get the full results of a previous Meta Council session, including all agent opinions and the synthesis.

  • get_visualization

    Fetch a chart artifact generated by a council session or LOCUS determination. Returns the machine-readable spec (the data behind the chart) plus the stable SVG URL, or the raw SVG itself with include_svg=true. Artifact ids appear in…

  • list_workflows

    List available multi-step workflow pipelines (composable bundles that chain several steps, each able to run on its own model/provider). Returns each workflow's slug, description, per-step model, and definition_sha — a fingerprint of that…

  • plan_workflow

    Preview what a workflow WOULD do, without running it. Costs nothing and runs no models: returns the step execution order, each step's role/model/max_tokens and whether it pauses for a human checkpoint, the workflow's declared parameters…

  • test_workflow_step

    Run exactly ONE step of a workflow and return what it produced, so you can iterate on a single step's wording without running the steps before it. THIS SPENDS CREDITS EXACTLY LIKE A REAL STEP: the step runs on a real model through the…

  • run_workflow

    Start a multi-step workflow pipeline and return its session id and definition_sha immediately by default — the fingerprint of the definition this run resolved, comparable against the one plan_workflow reported. Poll get_workflow_session…

  • get_workflow_session

    Poll a previously started workflow run for its current step-by-step status and output (useful when run_workflow timed out or is awaiting a checkpoint). Also returns that run's definition_sha — the fingerprint of the definition it resolved…

  • recommend_panel

    Recommend the best expert panel for a query (semantic match with keyword fallback). Returns the top panel + confidence and the runner-up options — feed the result into run_council's panel argument. Requires authentication because the…

  • estimate_cost

    Estimate what a panel or saved workflow would cost before running it: returns a per-agent/per-step price breakdown, the total for the requested number of runs, your remaining quota and platform credit, an honest list of any models the…

  • get_agent_detail

    Full detail on one expert agent by slug (from list_agents): role, description, default model, domain, tags, and tools.

  • advance_workflow

    Advance a workflow past a human checkpoint — approve or reject the paused step so the pipeline continues. Use the session id from run_workflow / get_workflow_session. Requires authentication.

  • retry_workflow

    Continue a stalled or finished workflow run from a chosen step. This starts a NEW run that reuses the outputs the original run already recorded and only executes — and only pays for — the steps from 'from_step' onward. The original run is…

  • get_settings

    Get the authenticated user's Meta Council settings — preferred model, plan tier, which credentials are saved (not live-verified), and the registry-backed tools that require, optionally use, or do not use account credentials. Names and…

  • list_integrations

    List which outside services the authenticated user has connected — ticket boards, stored connector credentials (name, kind, whether configured, and when last verified) and the connectors available to call them. Returns configured / not…

  • get_api_key_info

    Report the scopes, plan tier, expiry and remaining quota of the API key making this call, so an agent can check what it is allowed to do before attempting it rather than by being refused. Requires API-key authentication.

  • rotate_api_key

    Replace the API key making this call with a fresh one carrying the same scopes. WARNING: this IRREVERSIBLY deactivates the current key the moment it succeeds — every other caller using that key stops working immediately, so do not call it…

  • mint_child_api_key

    Mint a short-lived child API key for a delegated subtask. The child can never exceed the calling key: requested scopes must be a subset of what the caller holds, its expiry is capped by the caller's, and it may never itself mint keys…

  • list_outreach_campaigns

    List the authenticated user's outreach campaigns with current lead counts and recorded sent/replied workflow labels, not independently verified delivery or human-reply totals. Requires authentication.

  • search_outreach_leads

    Search the user's outreach leads — filter by a text query (company / contact / email), pipeline status, and/or campaign. Returns stable IDs, evidence, holds and exact rendered draft bytes/hash for review. Replies over 256 KiB refuse in…

  • outreach_analytics

    Outreach summary for the user — total leads, recorded status counts/ratios and incomplete outcome evidence. Requires authentication.

  • score_locus_case

    Score an anonymized adult mental-health / addiction case against LOCUS. Convenes the LOCUS Assessment Panel (psychiatrist, addiction specialist, clinical social worker, utilization reviewer, peer specialist, safety officer); each reviewer…

  • locus_determine_from_scores

    Compute a LOCUS Level of Care from dimension ratings you already have. Deterministic — no LLM, instant: composite + Determination Grid + the inviolable override floors (e.g. Risk-of-Harm=4 → minimum Level 5), applied in code. Provide…

  • ask_legal

    Request fixed legacy Themis source/citation records and attach a proposed Laws & Regulations agent/source/synthesis plan whose routes are planned_not_run. Check the law uses fixed legacy provider-record retrieval, but returned records do…

  • campaign_pipeline_stats

    Pipeline-stage breakdown for one outreach campaign — total / sent / active / won / lost workflow labels, recorded status ratio, and incomplete outcome evidence. Requires authentication.

  • list_campaign_triggers

    List automation triggers (auto-reply rules, status updates, notifications) configured for an outreach campaign. Requires authentication.

  • list_campaign_replies

    List sent / received emails for an outreach campaign, newest first — subject, body preview, and reply classification. Requires authentication.

  • create_outreach_campaign

    Create a new outreach campaign owned by the authenticated user. Returns the new campaign id. Reversible (campaigns can be edited/deleted in the dashboard). Requires authentication.

  • add_outreach_lead

    Add a single lead to the authenticated user's outreach book. Returns the new lead id. Provenance is stamped source="agent" server-side. Does not send any email. Requires authentication.

  • assign_leads_to_campaign

    Assign one or more of the user's existing leads to one of the user's campaigns (both must be owned by the caller). Returns how many were assigned. Idempotent. Requires authentication.

  • update_outreach_lead_status

    Advance a lead through the pipeline — set its status / pipeline stage and, optionally, a recorded reply, pitch, or notes. The core pipeline-drive action. Idempotent (setting the same status twice is a no-op). Requires authentication.

  • draft_outreach_email

    Save a draft email subject and/or body onto one of the user's leads. This only stores the draft for human review — it does NOT send anything. A human sends from the dashboard. Requires authentication.

  • create_outreach_pitch

    Create a reusable pitch template (subject + body templates, optional drafting prompt) owned by the user. Provenance is stamped source="agent" server-side. Returns the new pitch id. Requires authentication.

  • list_deals

    List the caller's sales deals (newest first) together with a weighted pipeline forecast (open/weighted/won totals). Optionally filter by stage or lead_id. Deals are private to the API-key owner.

  • get_deal

    Fetch one of the caller's deals by id with its full activity timeline (notes, calls, meetings, emails, tasks; newest first).

  • list_sales_tasks

    List the caller's open sales tasks (activities of type 'task' not yet done), bucketed overdue / today / upcoming and ordered most-urgent-first with per-bucket counts. Close one with complete_sales_task.

  • get_business_suite_overview

    What needs attention across my business? Return the same private, counts-only review as the browser: Sales tasks, Marketing approvals, Accounting runs and Consulting work, with deterministic next actions. Legal is a governed entry point…

  • get_sales_analytics

    Sales pipeline analytics for the caller: probability-weighted forecast, per-stage $ rollup, win rate (won / decided, by count and by value), average sales-cycle days over won deals, and open-deal aging with a stale count. Read-only…

  • get_sales_recommendations

    The caller's prioritized next-best sales actions: interested leads to convert, open deals gone stale enough to need a follow-up, and overdue tasks — each with a rationale and the exact governed tool to run next (convert_lead_to_deal /…

  • get_deal_health

    Health scores for the caller's OPEN deals: each scored 0-100 on how likely it is to be slipping (healthy >= 70 / watch / at_risk), worst first, with plain-language reasons — days since last logged contact, whether it is past its own…

  • create_deal

    Create a sales deal owned by the caller. Provide a title, or a lead_id to inherit the lead's company/name as the title. The deal appears live on the owner's Sales board. No deletes are exposed over MCP.

  • update_deal

    Update one of the caller's deals — most commonly to ADVANCE its stage (e.g. discovery -> proposal). Moving to closed_won/closed_lost stamps the close date; reopening to an open stage clears it. Only the fields you pass change; deal_id is…

  • convert_lead_to_deal

    Convert an owned outreach lead into a deal and advance the lead into the deal stage of the funnel (never downgrading an already-closed lead). Optional deal fields mirror create_deal; lead_id is required.

  • log_deal_activity

    Log an activity on a deal (or lead) — a note/call/meeting/email, or a follow-up task with a due date. Pass deal_id and/or lead_id (each must be owned by the caller). type defaults to 'note'; for a task set type='task' and a due_date…

  • complete_sales_task

    Mark one of the caller's sales tasks/activities done (or reopen it with done=false). Stamps or clears the completion time; activity_id is required.

  • list_invoices

    List the caller's invoices (newest first), optionally filtered by status (draft/sent/paid/void). Each entry includes its computed overdue flag.

  • get_invoice

    Fetch one of the caller's invoices by id, including its line items.

  • get_invoice_aging

    Summarize the caller's unpaid invoices by how long they have been past due. This owner-scoped, read-only report is computed live; an invoice is overdue only when its status is sent and its due_date is before today. Balances are separated…

  • create_invoice

    Create a draft invoice owned by the caller for a client, optionally seeded with line items and linked to an existing deal. Totals (subtotal/tax/total) are computed from the line items and tax_rate. The invoice starts in status 'draft'…

  • update_invoice

    Update a draft or sent invoice's header fields (client, terms, due date, tax rate, notes). Only the fields you pass change. Blocked once paid/void — void and re-issue instead. invoice_id is required.

  • add_invoice_line_item

    Add a billable line item to a draft or sent invoice; totals are recomputed automatically. Blocked once paid/void. invoice_id is required.

  • send_invoice

    Mark a draft invoice as sent (stamps issued_at). Re-sending an already-sent invoice is a harmless no-op. invoice_id is required.

  • mark_invoice_paid

    Mark a draft or sent invoice as paid (stamps paid_at). Cannot be applied to a void invoice. invoice_id is required.

  • void_invoice

    Void a draft or sent invoice. Cannot be applied to an already-paid invoice (issue a credit note instead). invoice_id is required. No delete tool is exposed over MCP — void is the terminal non-destructive state.

  • convert_deal_to_invoice

    Create a draft invoice from one of the caller's deals: one line item for the deal's amount, client_name defaulted from the deal's company/title. deal_id is required.

  • create_accounting_run

    Every new run requires one explicitly assigned entity and calendar tax_year in scope. Optional inclusive period_start/period_end must remain in that year. Unassigned source occurrences remain pending and excluded from amounts. Inspect…

  • list_accounting_runs

    List only the caller's private Accounting-run audit metadata, newest first. Raw source text and analysis results are intentionally omitted.

Las primeras 60 de 280, en el orden del servidor.

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": {
    "decision-intelligence": {
      "type": "http",
      "url": "https://meta-council.com/mcp"
    }
  }
}

Añadirlo

Claude Code, en una terminal

claude mcp add --transport http meta-council https://meta-council.com/mcp

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://meta-council.com/mcp como conector personalizado en los ajustes.

Especificación OpenAPI

537 rutas, leído el 2026-10-24. Abrir la especificación ↗

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.