get_my_context — TeamMeet MCP Tool Read-only
get_my_context
(get my context) 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 get_my_context from your client
- Claude Code TeamMeet get_my_context run in your project directory
- Claude Desktop TeamMeet get_my_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TeamMeet get_my_context ~/.cursor/mcp.json
- VS Code TeamMeet get_my_context .vscode/mcp.json
- Zed TeamMeet get_my_context ~/.config/zed/settings.json
- Windsurf TeamMeet get_my_context ~/.codeium/windsurf/mcp_config.json
- Cline TeamMeet get_my_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TeamMeet get_my_context ~/.gemini/settings.json
- Grok TeamMeet get_my_context .mcp.json (in your project root)
- ChatGPT TeamMeet get_my_context Settings → Connectors → Advanced → Developer mode
- Claude.ai TeamMeet get_my_context Settings → Connectors → Add custom connector
- LangChain TeamMeet get_my_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http teammeet https://teammeet.ai/mcpOther tools on this server
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.