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