Official Model Context Protocol (MCP) server for Cadence Meeting Intelligence
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"cadence-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Cadence MCP Server (Model Context Protocol) Official Model Context Protocol (MCP) server for the **Cadence Meeting & Speech Intelligence Platform**. Connects autonomous AI coding agents (**Cursor**, **Claude Desktop**, **Claude Code**, **Windsurf**, **Copilot**) directly to your team's live meeting context, verbal directives, anti-patterns, and architectural decisions. --- ## ⚡ What Cadence MCP Does 1. **Organizational Decision Verification:** Ask: *"Hey Claude, did we decide to go with MongoDB or Postgres in our architecture sync?"* Claude invokes `search_cadence_knowledge` to retrieve the exact spoken decision and quotes. 2. **Post-Meeting Code Handoff:** Ask: *"Implement the cache invalidation logic we just finished discussing."* Claude invokes `get_latest_meeting` to extract verified verbal directives and implementation rules. 3. **Meeting Discovery:** Query meetings by date or keyword (e.g. `list_meetings(query="sprint")`) to pull historical architectural constraints. 4. **Anti-Pattern Guardrails:** Automatically loads explicit architectural rejections (e.g. *"Do not introduce MongoDB into the relational service"*) so AI agents don't write disallowed code. --- ## 🛠️ MCP Tools Exposed | Tool Name | Arguments | Description | | :--- | :--- | :--- | | `search_cadence_knowledge` | `query: str`, `search_type: str = "all"`, `limit: int = 5` | Searches decisions, directives, and transcripts across all meetings the user attended. | | `list_meetings` | `query: str = None`, `date: str = None`, `limit: int = 5` | Lists past meetings with optional title or date filters. | | `get_latest_meeting` | *None* | Zero-argument shortcut fetching the compiled directives and constraints of the latest meeting. | | `get_meeting_context` | `meeting_id: str`, `include_transcript: bool = False` | Retrieves the full technical specification for a specific meeting ID. | --- ## 🚀 Setup & IDE Configuration ### Step 1: Generate Your API Key In your C…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.