Contio MeetingOS vs Meetbot MCP
A side-by-side look at the Contio MeetingOS and Meetbot MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Contio MeetingOS for workplace & productivity work; choose Meetbot MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Contio MeetingOS when
- You need dedicated capabilities in the Workplace & Productivity domain.
Choose Meetbot MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
MEETBOT_AUTH_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Contio MeetingOS | |
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 37/100 · Fair | 48/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | MEETBOT_AUTH_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Contio MeetingOS | View Meetbot MCP |
Tools & capabilities
Contio MeetingOS tools
No tool names declared yet. Check the project README from the listing page.
Meetbot MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Contio MeetingOS
No confirmed install command for Contio MeetingOS yet — follow the setup steps linked from its listing page rather than a guessed package name.
Meetbot MCP
{
"mcpServers": {
"poolside-ventures-meetbot-mcp": {
"command": "npx",
"args": [
"-y",
"@meetbot/mcp"
],
"env": {
"MEETBOT_AUTH_TOKEN": "YOUR_MEETBOT_AUTH_TOKEN_HERE"
}
}
}
}