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