List your agent

Meta Council

MCP server● Hosted · onlinev1.4.0

Multi-expert decision intelligence with transparent synthesis and auditable workflows

Reviews

No review yet. Used Meta Council? Be the first to help others choose.

What it does

Meta Council is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.4.0
PriceNot in the registry
First seen26 Sept 2026
Last checked1d ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 15h ago (live check)

Hosted endpoint

  • https://meta-council.com/mcp streamable-http

Required: X-API-Key (get it from the publisher)

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "meta-council": {
      "url": "https://meta-council.com/mcp",
      "headers": {
        "X-API-Key": "<your X-API-Key>"
      }
    }
  }
}

Replace the values in <angle brackets>.

Live check

Electra Index connected to the hosted endpoint 15h ago

ONLINE Meta Council answered an MCP connection on 16 Nov 2026 and introduced itself as meta-council 2.12.0 (MCP protocol 2025-06-18).

280 tools offered to AI assistants

  • 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 defa
  • 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 session
  • 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 de
  • 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 (va
  • 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 same
  • 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 for
  • 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 w
  • 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 query
Show 88 more
  • 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 platf
  • 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 l
  • 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 boole
  • 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 conf
  • 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 o
  • 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 (deleg
  • 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 full
  • 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 i
  • 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 EITHER
  • 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 no
  • 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, no
  • 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; compute
  • 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 / log_d
  • 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 expecte
  • 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 re
  • 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 (YYYY-M
  • 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 by
  • 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' — cal
  • 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 catal
  • list_accounting_runs · List only the caller's private Accounting-run audit metadata, newest first. Raw source text and analysis results are intentionally omitted.
  • get_accounting_run · Get one private Accounting run owned by the caller, including its deterministic estimates, disclaimer, engine revision, and audit timestamps. Source input stays omitted unless include_input=true is explicitly requested.
  • delete_accounting_run · Hide one owned Accounting run from normal lists and reads. Its encrypted data and provenance are retained and restore_accounting_run reverses this action; this is not permanent erasure. Repeating delete is safe. No external service is conta
  • restore_accounting_run · Restore one owned soft-deleted Accounting run to normal lists and reads, retaining its original encrypted data and provenance. Repeating restore is safe. No external service is contacted.
  • preview_accounting_ticket_sync · Preview, without writing, how one completed owned Accounting run's WRITEOff work plan would map to stable Meta Council tickets. Reports creates, updates, unchanged tickets, human-edited generated fields that will be preserved, and identity
  • sync_accounting_tickets · Commit a previously previewed completed Accounting run's WRITEOff work plan to stable owner-private Meta Council tickets. The expected_plan_hash from the preview is required, retries are idempotent, stable references prevent duplicate ticke
  • ticket_plan · Preview or idempotently commit an owner-private ticket tree generated from a planning prompt or supplied structured plan. Requires tickets:write. A preview without a supplied plan invokes the planner model and additionally requires councils
  • ticket_batch_create · Preview or idempotently commit one atomic owner-private batch of structured tickets and nested subtickets. Preview is non-mutating and returns the normalized commit payload, exact preview_token, and deterministic predicted IDs as JSON. Comm
  • ticket_list · Page through the caller's tickets on the Meta Council board. The opaque next_cursor is owner- and filter-bound; keep every filter unchanged on the next call. Immutable cursor ordering keeps a stable full-board traversal exact while returned
  • ticket_get · Full detail for one owned ticket: description, acceptance criteria, subticket progress, and the recent activity/comment trail. ticket_id is required. Use ticket_comments for complete bodies and older discussion pages.
  • ticket_comments · Read complete discussion bodies, authors, kinds and timestamps for one owned ticket, including archived tickets. Returns a JSON page, newest first with legacy null times last. limit is 1–100 (default 50). Continue with next_cursor while has
  • list_reviewed_attention · Discover latest owned attention reviews, including cleared, terminal, archived and unavailable work. Requires tickets:read. Filter unresolved (including withdrawn), resolved or all; independently set follow_up=due for saved follow-ups whose
  • get_ticket_attention_resolution · Inspect original reviewed evidence, a separately labeled fresh assessment and immutable owner resolution history. Requires tickets:read. limit 1–50, exclusive before_revision. Current state always refers to the latest review; unavailable wo
  • record_ticket_attention_resolution · Record or withdraw an owner resolution with a required explanation, latest review ID/revision, resolution revision and fresh assessment digest. Requires tickets:write. Use a stable idempotency key; exact retries return the original receipt,
  • get_ticket_attention_policy · Read the owner-private effective attention policy, built-in defaults, applicable statuses and immutable history. Requires tickets:read. limit 1–50 (default 20); exclusive before_revision. Earlier unrecorded history is unknown. No writes or
  • save_ticket_attention_policy · Save owner-private attention thresholds in UTC days (finite 0–3650), status overrides and optional paused_statuses. Requires tickets:write. Supply full base thresholds, sparse overrides, expected_revision and caller-stable idempotency_key.
  • get_ticket_attention_review · Read the owner-private current attention assessment, latest review and immutable history. Requires tickets:read. History uses limit 1–50 (default 20) and exclusive before_revision; stays readable after ticket closure/archive/deletion. Evide
  • save_ticket_attention_review · Record an owner-private review of current attention evidence, with optional note (2000 characters) and follow_up_date plus explicit IANA follow_up_timezone, or null for both. Requires tickets:write. Supply the current evidence digest, curre
  • get_ticket_attention_queue · Read the same ranked Needs attention queue as the browser and REST. Returns complete JSON with reasons, UTC clock evidence, effective owner policy thresholds and revision, approximation flags, unmet prerequisites and suggested next actions.
  • get_ticket_projects · Projects overview of the caller's board: one entry per top-level epic with recursive descendant progress (done %, counts by status, blocked, points, sub-epics, last activity), plus a triage strip of unrouted work (backlog + unassigned root
  • get_workspace_metrics · One cross-domain rollup of the caller's own workspace: council sessions (total, last 30 days, by status, tokens), feedback ratings, tickets (open/done), deals (count by stage, open pipeline value) and invoices (count by status, outstanding
  • get_meta_council_platform_metrics · OPERATOR ONLY: cross-owner analytics for the META COUNCIL PLATFORM itself — every account added together, NOT the caller's workspace (use get_workspace_metrics for that). Requires both the platform:admin scope AND an ADMIN_EMAILS operator a
  • get_site_analytics · OPERATOR ONLY: visitor traffic for the META COUNCIL PLATFORM's own website — every visitor added together, NOT the caller's workspace (use get_workspace_metrics for that) and NOT the business rollup (use get_meta_council_platform_metrics fo
  • get_feature_delivery_summary · Read one owned feature epic's current task completion, estimates, weekly delivery flow, lead/cycle evidence, risks and throughput scenario. Includes a separate retained-history view of scope additions/removals, estimate changes and accumula
  • get_ticket_burndown · Daily burndown series replayed from the append-only ticket ledger: per-day scope (existing, non-cancelled), remaining, done levels plus added/completed flows, with a summary. Optionally scope to one epic's current subtree via root_id. Backf
  • get_ticket_label_history · Read immutable owner-private observed label assignments/removals, revision bindings and legacy limits. Retains deleted tickets. Bounded cursor pagination; no provider or ticket changes.
  • get_ticket_label_cohort · Report a fixed cohort holding one exact label at the UTC window start, observed daily task completions/reopens, status and point coverage. Today's labels never rewrite history. end_date is exclusive; default today UTC. Bounded cursor pagina
  • list_saved_views · List saved ticket views you can open: the stored filter, column, grouping and sort combinations saved by you, plus any shared with a team you belong to. Shared views appear under the active and all scopes and never once archived, because an
  • get_saved_view · Fetch one saved ticket view's definition by id: its name, filters, columns, grouping, sort and whether it is shared. This returns the view itself, not the tickets it selects -- use execute_saved_view to run it. A view you cannot read is rep
  • execute_saved_view · Run saved ticket, attention or reviewed-work intent against live owned data. Ordinary views return matching tickets and optional group counts. Triage returns the original reader envelope in data, the view and a definition_token. For triage
  • list_portfolio_report_history · Browse owned saved reports in portfolio (default), project or all scopes, newest first. Project scope requires project_id. Each report supplies its immutable ID and payload hash for comparisons or replacement declarations. Continue with nex
  • get_portfolio_report_lineage · Read bounded outgoing replacement chains and incoming owner declarations for one owned saved report. Absence means no replacement recorded, not approval. Continue outgoing pages with next_snapshot_id and incoming pages with next_before_rela
  • get_portfolio_snapshot_inputs · Verify and return the retained minimal inputs and regenerated counts of one owned project report. Reads stored inputs only; later ticket moves or deletion do not recapture the report. Legacy reports without retained inputs return a precise
  • export_portfolio_snapshot · Download one owned saved report using the same JSON, CSV, accessible HTML or optional tagged PDF renderer as the browser. Returns filename, media_type, encoding, content and SHA-256; PDF content is base64. Unsupported PDF fonts or renderer
  • supersede_portfolio_report · Record that one owned saved report replaces another, with a required reason and both fetched payload hashes. This is an immutable owner declaration, not approval, sharing or a claim of accuracy. Both reports must have no replacement recorde
  • list_portfolio_snapshots · List your own portfolio (default), project or all snapshots, newest first. Project scope requires project_id: the immutable rollups of how your ticket portfolio stood at the moments you captured them. Each carries its label, schema version,
  • get_portfolio_snapshot · Fetch one portfolio snapshot by id: its label, schema version, the exact stored rollup payload, its content hash, who recorded it and when. The payload is served from storage and is never recomputed from live tickets, so a snapshot read tod
  • diff_portfolio_snapshots · Compare two of your own portfolio snapshots and return the per-dimension movement between them. snapshot_id is always the 'to' side; against is the 'from' baseline, defaulting to your newest snapshot in the same project or portfolio strictl
  • list_portfolio_snapshot_notes · Read the decision and comment thread recorded against one of your portfolio snapshots, oldest first. Each note carries the snapshot content hash it was written against plus binding_intact comparing that hash to the snapshot's hash now, so a
  • create_saved_view · Save a named ticket filter, column, grouping and sort bundle so you can reopen it later or share it with a team. Saves the QUESTION, not an answer: the view is re-run against live tickets every time it is opened, so it never goes stale. The
  • update_saved_view · Revise one of YOUR OWN saved views in place, keeping its id and any existing team share. Only the fields you send change; the rest are left exactly as they were, while scorecard-enrolled views require the current definition_revision; after

The first 100 are shown.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://meta-council.com/mcpDECLAREDSRC-001 Official MCP Registry1d ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry1d ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry1d ago
Repositoryhttps://github.com/daliu/meta-councilDECLAREDSRC-001 Official MCP Registry1d ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry1d ago
Version1.4.0DECLAREDSRC-001 Official MCP Registry1d ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry1d ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run Meta Council? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor Meta CouncilLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of Meta Council?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/meta-council?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/meta-council/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about Meta Council

How do I connect Meta Council?

Use the hosted endpoint https://meta-council.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

Does Meta Council need an API key or token?

Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.

What tools does Meta Council offer?

When Electra Index connected on 16 Nov 2026, it listed 280 tools: run_council, plan_council, list_panels, list_agents, get_session, get_visualization, list_workflows, plan_workflow and more. The full list is in "Live check" above.

Is Meta Council online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 15h ago.