roki_audit_integration — ROKI Connect MCP Tool
roki_audit_integration
(roki audit integration) is one of 19 tools on the
ROKI Connect
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call roki_audit_integration from your client
- Claude Code ROKI Connect roki_audit_integration run in your project directory
- Claude Desktop ROKI Connect roki_audit_integration ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ROKI Connect roki_audit_integration ~/.cursor/mcp.json
- VS Code ROKI Connect roki_audit_integration .vscode/mcp.json
- Zed ROKI Connect roki_audit_integration ~/.config/zed/settings.json
- Windsurf ROKI Connect roki_audit_integration ~/.codeium/windsurf/mcp_config.json
- Cline ROKI Connect roki_audit_integration ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ROKI Connect roki_audit_integration ~/.gemini/settings.json
- Grok ROKI Connect roki_audit_integration .mcp.json (in your project root)
- ChatGPT ROKI Connect roki_audit_integration Settings → Connectors → Advanced → Developer mode
- Claude.ai ROKI Connect roki_audit_integration Settings → Connectors → Add custom connector
- LangChain ROKI Connect roki_audit_integration pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http connect https://mcp.roki.la/mcpOther tools on this server
- roki_search_docs
- roki_get_doc_section
- roki_list_operations
- roki_get_operation
- roki_get_schema
- roki_get_error
- roki_validate_request
- roki_check_result
- roki_get_integration_example
- roki_get_quickstart
- roki_get_authentication_guide
- roki_get_webhook_guide
- roki_choose_integration_mode
- roki_verify_webhook_signature
- roki_scaffold_integration
- roki_sandbox_try
- roki_sandbox_info
- roki_status
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.