draw — TeamMeet MCP Tool
draw
(draw) is one of 25 tools on the
TeamMeet
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call draw from your client
- Claude Code TeamMeet draw run in your project directory
- Claude Desktop TeamMeet draw ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TeamMeet draw ~/.cursor/mcp.json
- VS Code TeamMeet draw .vscode/mcp.json
- Zed TeamMeet draw ~/.config/zed/settings.json
- Windsurf TeamMeet draw ~/.codeium/windsurf/mcp_config.json
- Cline TeamMeet draw ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TeamMeet draw ~/.gemini/settings.json
- Grok TeamMeet draw .mcp.json (in your project root)
- ChatGPT TeamMeet draw Settings → Connectors → Advanced → Developer mode
- Claude.ai TeamMeet draw Settings → Connectors → Add custom connector
- LangChain TeamMeet draw pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http teammeet https://teammeet.ai/mcpOther tools on this server
- start_meeting
- invite
- list_meetings
- get_transcript
- get_notes
- get_action_items
- send_message
- speak
- list_recordings
- send_feedback
- submit_fix
- import_transcript
- send_notetaker
- my_tasks
- get_task
- update_task
- join_meeting
- listen
- hand_off
- set_up_booking_page
- booking_page_status
- find_times
- book_time
- get_my_context
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.