Supported MCP clients
Oprex MCP works with every client that supports Streamable HTTP. Below are guides for the most common ones.
Claude Code (CLI)
Run this in your terminal:
claude mcp add --transport http oprex-sdlc https://api.oprex.id/mcp \
--header "Authorization: Bearer <YOUR_API_KEY>"
Claude Desktop
Settings → Developer → Edit Config, then add (using the mcp-remote bridge for the remote server):
{
"mcpServers": {
"oprex-sdlc": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.oprex.id/mcp",
"--header", "Authorization: Bearer <YOUR_API_KEY>"]
}
}
}
Claude.ai (web) — Settings → Connectors
Open Settings → Connectors → Add custom connector, fill in a Name (e.g. "Oprex") and the Remote MCP server URL https://api.oprex.id/mcp.
Leave OAuth Client ID/Secret empty — Oprex supports Dynamic Client Registration, so Claude registers itself. After saving, Claude sends you to the Kinexa login page and then to Oprex's consent screen; click Allow and the connector is live.
Cursor
Create ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"oprex-sdlc": {
"url": "https://api.oprex.id/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}
VS Code (GitHub Copilot)
Create .vscode/mcp.json in your workspace:
{
"servers": {
"oprex-sdlc": {
"type": "http",
"url": "https://api.oprex.id/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}
The Cline / Continue extensions also support MCP — add the same URL & header in their MCP settings.
Kilo Code
Kilo Code is a VS Code extension (a Cline/Roo fork) that runs a local coding agent. Add the Oprex MCP server via its UI — Settings → MCP → Add server, HTTP/Streamable type, URL https://api.oprex.id/mcp and the header Authorization: Bearer oprex_pk_… — or write the config file directly:
{
"mcpServers": {
"oprex-sdlc": {
"url": "https://api.oprex.id/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}
Place it at .kilocode/mcp.json in your workspace, or ~/.kilocode/mcp.json for all users.
Google Gemini CLI
Edit ~/.gemini/settings.json:
{
"mcpServers": {
"oprex-sdlc": {
"httpUrl": "https://api.oprex.id/mcp",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}
ChatGPT
ChatGPT supports MCP via Developer Mode / Custom Connectors (Plus/Pro/Enterprise). Enter the URL https://api.oprex.id/mcp.
ChatGPT's connector UI favours OAuth over a static API-key header — which Oprex now supports: just enter the URL, leave the OAuth fields empty, and approve on Oprex's consent screen.
Ollama
Ollama runs local models but isn't itself an MCP client. Use an MCP-capable app with your Ollama model — e.g. Cline or Continue in VS Code (pointed at an Ollama model), or LibreChat — then add Oprex as an MCP server there (same URL & header as above).
For stdio-based clients, use the bridge:
npx -y mcp-remote https://api.oprex.id/mcp \
--header "Authorization: Bearer <YOUR_API_KEY>"
Antigravity
Open Settings → MCP → Add server, choose HTTP type, set the URL https://api.oprex.id/mcp and header Authorization: Bearer oprex_pk_…. If only stdio is supported, use the bridge config mcp-remote as in Claude Desktop.
Xcode
Xcode has no built-in MCP client yet. The easiest path: run a coding agent (e.g. Claude Code in Terminal, or Cursor) inside your Xcode project folder — it can read your code and use Oprex MCP to manage issues/requirements. Follow the Claude Code or Cursor sections above.
Any MCP client / universal bridge
Any MCP client supporting Streamable HTTP: use the URL & header above. For stdio-only clients, bridge with mcp-remote:
npx -y mcp-remote https://api.oprex.id/mcp \
--header "Authorization: Bearer <YOUR_API_KEY>"