agent-get-started — three.ws for Grok MCP Prompt
agent-get-started
is one of 4 prompts on the
three.ws for Grok
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke agent-get-started from your client
- Claude Code three.ws for Grok Prompt/agent-get-started run in your project directory
- Claude Desktop three.ws for Grok Prompt/agent-get-started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor three.ws for Grok Prompt/agent-get-started ~/.cursor/mcp.json
- VS Code three.ws for Grok Prompt/agent-get-started .vscode/mcp.json
- Zed three.ws for Grok Prompt/agent-get-started ~/.config/zed/settings.json
- Windsurf three.ws for Grok Prompt/agent-get-started ~/.codeium/windsurf/mcp_config.json
- Cline three.ws for Grok Prompt/agent-get-started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI three.ws for Grok Prompt/agent-get-started ~/.gemini/settings.json
- Grok three.ws for Grok Prompt/agent-get-started .mcp.json (in your project root)
- ChatGPT three.ws for Grok Prompt/agent-get-started Settings → Connectors → Advanced → Developer mode
- Claude.ai three.ws for Grok Prompt/agent-get-started Settings → Connectors → Add custom connector
- LangChain three.ws for Grok Prompt/agent-get-started pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 14 November 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.