Other MCP Clients
All clients below connect to https://api.cloudsek.com/mcp. The config
structure is identical to the Claude Desktop JSON block; substitute the correct
file path for your tool.
Quick reference
| Client | Config file path |
|---|---|
| Cursor | ~/.cursor/mcp.json (global) or .cursor/mcp.json (project). Recommended: use Cursor Settings → MCP in the UI. |
| Amazon Q Developer CLI | ~/.aws/amazonq/mcp.json (global) or .amazonq/mcp.json (workspace). Note: Amazon Q CLI is superseded by Kiro. |
OpenRouter
OpenRouter is an AI model router and API proxy. It routes prompts to models like Claude, GPT-4o, and Gemini via a unified API. It is not an MCP client itself and does not connect directly to MCP servers.
If you use OpenRouter as your AI backend inside a tool that also supports MCP (such as Cursor, Kiro, or VS Code with Continue.dev), configure CloudSEK MCP in that tool's MCP settings using the JSON format shown in the setup pages. The CloudSEK MCP server works with any underlying AI model.
| Scenario | What to do |
|---|---|
| Cursor with OpenRouter backend | Add CloudSEK to ~/.cursor/mcp.json using the standard JSON format. Cursor handles MCP independently from the model provider. |
| Kiro with custom model provider | Add CloudSEK to .kiro/settings/mcp.json as shown in the Kiro setup. Model routing and MCP are configured independently. |
| Continue.dev (VS Code extension) | Add CloudSEK to Continue's config.json under mcpServers, using url and headers. |
| Custom agent or script | Connect to https://api.cloudsek.com/mcp using any MCP client SDK, passing Authorization and X-CloudSEK-Org-Id headers. |