my_tasks — Meetful MCP Tool

my_tasks (my tasks) is one of 23 tools on the Meetful MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call my_tasks from your client

Claude Code Meetful my_tasks run in your project directory
Claude Desktop Meetful my_tasks ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Meetful my_tasks ~/.cursor/mcp.json
VS Code Meetful my_tasks .vscode/mcp.json
Zed Meetful my_tasks ~/.config/zed/settings.json
Windsurf Meetful my_tasks ~/.codeium/windsurf/mcp_config.json
Cline Meetful my_tasks ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Meetful my_tasks ~/.gemini/settings.json
Grok Meetful my_tasks .mcp.json (in your project root)
ChatGPT Meetful my_tasks Settings → Connectors → Advanced → Developer mode
Claude.ai Meetful my_tasks Settings → Connectors → Add custom connector
LangChain Meetful my_tasks pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http meetful https://meetful.com/mcp

Other tools on this server

start_meeting
invite
list_meetings
get_transcript
get_notes
get_action_items
send_message
list_recordings
send_feedback
submit_fix
import_transcript
send_notetaker
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 14 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.

Meetful MCP server