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