Skip to main content
Claude Code manages servers through CLI commands instead of JSON config files. Servers can be scoped globally (all projects) or per-project.

Setup

1

Set your API key

Add your OpenCX API key to your shell profile so it persists across sessions:
2

Add the MCP server

This registers the server at user scope (available in all projects) by default.
Prefer zero install? Connect to the hosted endpoint instead — same tools, nothing to keep updated:
3

Verify

Start Claude Code and ask: “List my recent chat sessions.”You can also confirm the server is registered:

Scope

Claude Code supports two scopes for MCP servers: Add at project scope when your team should share the same MCP setup:
Project-scoped servers read environment variables from the shell of whoever runs Claude Code. Each team member sets OPENCX_API_KEY in their own shell profile.

Managing Servers

CI and Automation

Claude Code can use MCP servers in non-interactive contexts. Pass the API key through CI secrets:
For headless use, Claude Code’s --print flag outputs the response to stdout without an interactive session.

Claude Desktop

JSON config and app restart flow

Get Started

API key setup and all client configs

Prompt Library

Ready-to-use prompts by domain

Troubleshooting

Common issues and fixes