Connect Oprex to your AI assistant
A Model Context Protocol (MCP) server for Oprex ALM/SDLC. Give Claude, ChatGPT, Gemini, or your IDE direct access to your projects, issues, requirements, milestones, releases, tests, and pipelines — read and write — with a single API key.
What is Oprex MCP?
MCP is an open standard that lets AI models call "tools" on external services. Oprex MCP exposes your SDLC data as tools, so an AI assistant can answer questions like "how many open high-severity issues?" or take actions like "create a new requirement" — right inside your Oprex workspace, scoped to your tenant and permissions.
Endpoint: POST https://oprex.id/mcp — JSON-RPC 2.0 (Streamable HTTP, stateless). Auth: header Authorization: Bearer oprex_pk_….
What you can do
- Browse projects & groups, resolve a path like
indohrm/enterprise - Read & filter issues, requirements, milestones, releases, specs, tickets, tests, pipelines
- Create & update issues (bugs) and requirements
- View the coverage matrix (requirement→test traceability)
Write actions require an API key with the write scope.
Version & releases
v1.1.0 · current
- +6 tools:
get_project,list_tickets,list_test_cases,list_pipelines,list_release_plans,coverage_matrix - Multi-client docs page (dual EN/ID)
v1.0.0
- Initial release: 12 tools (projects, groups, resolve, issues CRUD, requirements, milestones, releases, specs)
- Streamable HTTP + API-key auth
1. Create an API key
Open member.oprex.id/panel/settings/api-keys → create a key. Choose scope read (safe, read-only) or write. Copy the key oprex_pk_… — shown only once.
Claude Code (CLI)
Run this in your terminal:
claude mcp add --transport http oprex https://oprex.id/mcp \
--header "Authorization: Bearer oprex_pk_XXXXXXXX"Claude Desktop
Settings → Developer → Edit Config, then add (using the mcp-remote bridge for the remote server):
{
"mcpServers": {
"oprex": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://oprex.id/mcp",
"--header", "Authorization: Bearer oprex_pk_XXXXXXXX"]
}
}
}Cursor
Create ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):
{
"mcpServers": {
"oprex": {
"url": "https://oprex.id/mcp",
"headers": { "Authorization": "Bearer oprex_pk_XXXXXXXX" }
}
}
}VS Code (GitHub Copilot)
Create .vscode/mcp.json in your workspace:
{
"servers": {
"oprex": {
"type": "http",
"url": "https://oprex.id/mcp",
"headers": { "Authorization": "Bearer oprex_pk_XXXXXXXX" }
}
}
}
The Cline / Continue extensions also support MCP — add the same URL & header in their MCP settings.
Google Gemini CLI
Edit ~/.gemini/settings.json:
{
"mcpServers": {
"oprex": {
"httpUrl": "https://oprex.id/mcp",
"headers": { "Authorization": "Bearer oprex_pk_XXXXXXXX" }
}
}
}ChatGPT
ChatGPT supports MCP via Developer Mode / Custom Connectors (Plus/Pro/Enterprise). Enter the URL https://oprex.id/mcp.
Honest note: ChatGPT's connector UI currently favours OAuth / no-auth and doesn't expose a static API-key header field. For now, use Oprex MCP from ChatGPT via the Agents/Responses API (where you can set headers), or wait for Oprex OAuth (on the roadmap). For a no-code path, Claude Code/Desktop, Cursor, or Gemini CLI are the easiest.
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://oprex.id/mcp \
--header "Authorization: Bearer oprex_pk_XXXXXXXX"Antigravity
Open Settings → MCP → Add server, choose HTTP type, set the URL https://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://oprex.id/mcp \
--header "Authorization: Bearer oprex_pk_XXXXXXXX"Tools reference
| Tool | Scope | Description |
|---|---|---|
oprex_list_projects | read | List all projects in your Oprex tenant (GitLab-style). Returns id, name, slug, groupId, visibility. |
oprex_list_groups | read | List all groups (namespaces) in your Oprex tenant. Returns id, name, path. |
oprex_resolve_project | read | Resolve a GitLab-style path <group>/<project> to its group + project records. Use to turn a human path like 'indohrm/enterprise' into ids. |
oprex_list_issues | read | List issues (bugs) — optionally scoped to a project and filtered by status/severity/text. |
oprex_get_issue | read | Get a single issue (bug) by id, with full detail. |
oprex_create_issue | write | Create a new issue (bug). Requires a write-scoped API key. |
oprex_update_issue | write | Update an issue (bug): status, severity, title, or description. Requires a write-scoped API key. |
oprex_list_requirements | read | List requirements — optionally scoped to a project and filtered by status/type/text. |
oprex_create_requirement | write | Create a new requirement. Requires a write-scoped API key. |
oprex_list_milestones | read | List milestones — optionally scoped to a project and filtered by status. |
oprex_list_releases | read | List releases (Staging → RC → Stable) — optionally scoped to a project. |
oprex_list_specifications | read | List specifications (technical designs) — optionally scoped to a project. |
oprex_get_project | read | Get a single project by id, with full detail (visibility, group, git repo, type). |
oprex_list_tickets | read | List support/helpdesk tickets — optionally scoped to a project and filtered by status/text. |
oprex_list_test_cases | read | List test cases (TestLink-style scenarios) — optionally scoped to a project. |
oprex_list_pipelines | read | List CI/CD pipelines and their runs — optionally scoped to a project. |
oprex_list_release_plans | read | List release plans (roadmap of planned releases) — optionally scoped to a project. |
oprex_coverage_matrix | read | Get the requirement→test coverage matrix for a project (traceability). |
Security & scopes
- Every call is scoped to the API key's tenant — no cross-tenant access.
- Scopes:
read(read-only),write(create/update). Grant the least scope needed. - Revoke a key anytime in the panel if leaked.
- Treat the key like a password — never commit it to a public repo.
FAQ
Is it free? Yes, included with your Oprex subscription.
Can multiple AIs use it at once? Yes — the same endpoint & key work across all MCP clients.
What about OAuth for claude.ai / ChatGPT web? On the roadmap. For now use clients that support an API-key header.