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