Chmeetings

@chmeetings show me all meetings scheduled for this week with their agendas and participant lists

Here are your meetings for the week of January 13-19, 2025: **Monday, Jan 13** – Product Roadmap Review (2:00 PM, 60 min) with Sarah Chen, Mike Torres, and 4 others. Agenda: Q1 feature prioritization, resource allocation. **Wednesday, Jan 15** – Sprint Planning (10:00 AM, 90 min) with Engineering team (8 participants). Agenda: Sprint 24 scope, dependency review. **Friday, Jan 17** – Client Check-in: Acme Corp (3:00 PM, 30 min) with Lisa Park, client stakeholders. Agenda: Project status update, next milestone discussion. All times shown in your local timezone (PST).

This read-only query demonstrates calendar retrieval and agenda parsing. Requires API key with read access to your organization's meeting data. The MCP returns structured meeting metadata; actual availability depends on how your team logs meetings in Chmeetings.

@chmeetings create a 30-minute retrospective meeting for next Tuesday at 2pm with the design team, agenda item: discuss last sprint's UX feedback

Meeting created successfully: **Sprint 23 Retrospective** Tuesday, January 21, 2025 at 2:00 PM PST Duration: 30 minutes Participants: Design team (6 members invited) Agenda: Discuss last sprint's UX feedback Calendar invites sent to all participants. Meeting ID: mtg_8x4k2p9. You can update details or add notes in Chmeetings before the meeting starts.

This write operation creates a meeting record and triggers calendar invitations. Requires API key with write permissions. The MCP schedules based on your organization's timezone settings and participant availability rules configured in Chmeetings—conflicts may require manual resolution.

@chmeetings pull notes and action items from yesterday's engineering sync, then draft a summary email I can send to stakeholders who weren't there

Based on the January 12 Engineering Sync notes: **Draft Summary Email:** Subject: Engineering Sync Update – Jan 12 Hi team, Key updates from yesterday's sync: - API v3 migration is 70% complete; targeting Jan 25 for staging deployment - Database performance issue resolved; query times reduced by 40% - New hire onboarding: Jamie starts Monday, will pair with Alex on auth service **Action Items:** - Sarah: finalize load testing scenarios by EOW - Mike: review security audit findings, report back Wednesday - Team: code freeze begins Jan 24 for release prep Let me know if you need more detail on any item. This draft pulls directly from meeting notes—feel free to edit tone or add context before sending.

This synthesis example combines meeting data retrieval with AI-generated communication. The quality of the summary depends on how thoroughly your team documents notes in Chmeetings during meetings. Action item extraction works best when participants explicitly tag tasks in the original notes.

When you need meeting notes turned into trackable tasks

A 6-person ops team runs three client calls a week and loses half the follow-ups in Slack threads. Chmeetings solves this if your workflow is record-transcribe-extract-assign. The API key auth means one person sets it up and the whole team benefits. The trade-off: if your meetings are already structured (agendas in Notion, notes in Linear), adding another tool creates duplicate entry points. This MCP wins when your current process is chaotic and you need a forcing function to capture commitments before people leave the Zoom. If your team already has a notes system they trust, skip this and keep using what works.

When distributed teams need meeting recaps without re-watching

A 12-person product team spans four time zones and records standups for the late shift. Chmeetings makes sense if you need AI-generated summaries that people can scan in under two minutes. The API key setup is one-time; after that, summaries flow into Slack or email without manual work. The boundary: if your standups are under 15 minutes and already well-structured, a summary adds little value. This MCP pays off when meetings run long, wander off-topic, or include stakeholders who skip the live call but need the decisions. If your team is co-located or meetings are tight, the juice isn't worth the squeeze.

When support or sales calls need searchable takeaways

A 4-person customer success team does 20 calls a week and can't remember which client asked about which feature. Chmeetings works if you need a searchable archive of what was said, who said it, and when. The API key auth means the CS lead configures it once and everyone's calls get processed automatically. The limit: if your CRM already captures call notes and your team actually fills them out, this duplicates effort. This MCP wins when call notes are inconsistent or missing, and you need a fallback that doesn't rely on human discipline. If your team is diligent about logging calls manually, stick with your CRM and save the integration overhead.