Convo

Created By
itsconvo2 months ago
Access your meetings, transcripts, summaries, and action items from Convo, an AI meeting assistant. Cross-meeting intelligence: prepare for calls with past context, get weekly digests, and track action items across all meetings. Works before, during, and after your meetings.
Overview

Convo MCP Server

Convo is an AI meeting assistant that helps you before, during, and after your calls.

Tools

Single meeting:

  • list_meetings - List and search your meetings
  • get_transcript - Full transcript with speaker names and timestamps
  • get_summary - Key points, decisions, and action items
  • get_feedback - AI coaching feedback with communication scores
  • ask_about_meeting - Ask any question about a meeting
  • draft_followup_email - Draft follow-up emails referencing actual discussion points
  • share_meeting - Generate a shareable link
  • get_upcoming_meetings - View upcoming calendar events
  • get_account_info - Check your plan and API usage

Cross-meeting intelligence:

  • prepare_for_meeting - Briefing from all past meetings with a person or company
  • weekly_digest - Consolidated digest across all meetings in a time period
  • find_action_items - All action items across meetings, filterable by owner

Prompts

  • meeting-prep - One-click briefing before any call
  • weekly-review - Consolidated weekly meeting summary
  • follow-up-blitz - Batch draft follow-up emails for recent meetings

Setup

  1. Download the Convo app at itsconvo.com (requires Starter plan or above)
  2. Generate an API key in your dashboard settings
  3. Install: npm install -g @itsconvo/mcp-server

Server Config

{
  "mcpServers": {
    "convo": {
      "command": "npx",
      "args": [
        "-y",
        "@itsconvo/mcp-server"
      ],
      "env": {
        "CONVO_API_KEY": "convo_your_api_key_here"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
itsconvo
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago