Nx Console vs Ocireg MCP
A side-by-side look at the Nx Console and Ocireg MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nx Console for developer tools work as a local process; choose Ocireg MCP for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nx Console when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose Ocireg MCP when
- You need dedicated capabilities in the Developer Tools domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
OCI_TOKEN, OCI_USERNAME, OCI_PASSWORD, MCP_PORT. - You want tools like
image_ref, repository.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 51/100 · Good | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | OCI_TOKENOCI_USERNAMEOCI_PASSWORDMCP_PORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,412 | 13 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Nx Console | View Ocireg MCP |
Tools & capabilities
Nx Console tools
No tool names declared yet. Check the project README from the listing page.
Ocireg MCP tools 2
image_refThe image reference (e.g., docker.io/library/alpine:latest)repositoryThe repository name (e.g., docker.io/library/alpine)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Nx Console
{
"mcpServers": {
"nx-console": {
"command": "npx",
"args": [
"-y",
"create-nx-workspace@latest"
]
}
}
}
Ocireg MCP
No confirmed install command for Ocireg MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Nx Console is categorized under Developer Tools and uses a local stdio subprocess. Ocireg MCP belongs to Developer Tools and uses an install path we have not confirmed yet. Pick Nx Console for developer tools work and Ocireg MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Ocireg MCP has no confirmed install command yet — follow its own setup instructions.
Nx Console has no declared pricing — check the project's own site. Ocireg MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add nx-console and stackloklabs-ocireg-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nx Console has a quality signal of 51/100 (Good) with 2 views, 0 installs and 1,412 GitHub stars. Ocireg MCP has 52/100 (Good) with 2 views, 0 installs and 13 GitHub stars.