first_play — GTM Otto MCP Prompt

first_play is one of 3 prompts on the GTM Otto MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke first_play from your client

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

Other prompts on this server

• weekly_review
• instantly_handoff

GTM Otto also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.