get_my_context — Meetful MCP Tool Read-only

get_my_context (get my context) 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 get_my_context from your client

Claude Code Meetful get_my_context run in your project directory
Claude Desktop Meetful get_my_context ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Meetful get_my_context ~/.cursor/mcp.json
VS Code Meetful get_my_context .vscode/mcp.json
Zed Meetful get_my_context ~/.config/zed/settings.json
Windsurf Meetful get_my_context ~/.codeium/windsurf/mcp_config.json
Cline Meetful get_my_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Meetful get_my_context ~/.gemini/settings.json
Grok Meetful get_my_context .mcp.json (in your project root)
ChatGPT Meetful get_my_context Settings → Connectors → Advanced → Developer mode
Claude.ai Meetful get_my_context Settings → Connectors → Add custom connector
LangChain Meetful get_my_context 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
my_tasks
get_task
update_task
join_meeting
listen
hand_off
set_up_booking_page
booking_page_status
find_times
book_time

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