Skip to content

Configure MCP in the terminal

This guide shows how to load the NEO MCP servers (playwright, jira, azure-devops) from each assistant's command line. It's useful if you work in the terminal, or if you prefer running a command over editing a file by hand. Before you start, check Configure the MCPs to see which servers you need and what data goes into each one.

Assistant Command to add File where it's saved How to check
Claude Code CLI claude mcp add .mcp.json or ~/.claude.json /mcp · claude mcp list
Codex CLI codex mcp add ~/.codex/config.toml /mcp · codex mcp list
GitHub Copilot CLI /mcp add ~/.copilot/mcp-config.json or .mcp.json /mcp show <nombre>

Claude Code CLI

The CLI and the VS Code extension use the same configuration: whatever you add here also appears in the IDE (and in the Code tab of Claude Desktop).

Add the servers

The options go before the name, and -- separates the command that launches the server:

# Playwright — in the project (saved in .mcp.json)
claude mcp add --transport stdio --scope project playwright -- npx -y @playwright/mcp@latest --browser chromium

# Jira
claude mcp add --transport stdio --scope project \
  --env JIRA_URL=https://your-site.atlassian.net/ \
  --env JIRA_USERNAME=your.email@company.com \
  --env JIRA_API_TOKEN=<token> \
  --env CONFLUENCE_URL=https://your-site.atlassian.net/wiki \
  --env CONFLUENCE_USERNAME=your.email@company.com \
  --env CONFLUENCE_API_TOKEN=<token> \
  --env READ_ONLY_MODE=true \
  jira -- uvx mcp-atlassian

# Azure DevOps
claude mcp add --transport stdio --scope project \
  --env AZURE_DEVOPS_ORG_URL=https://dev.azure.com/your-org \
  --env AZURE_DEVOPS_AUTH_METHOD=pat \
  --env AZURE_DEVOPS_PAT=<token> \
  azure-devops -- npx -y @tiberriver256/mcp-server-azure-devops

If you already have the JSON ready, you can pass it in full with claude mcp add-json <nombre> '<json>'.

Which scope should you choose? (--scope)

--scope Where it's saved Recommended for
project .mcp.json in the repository root NEO (check that .mcp.json is in .gitignore if it has tokens)
local (the one used if you don't specify any) ~/.claude.json, only for that project Trying something without touching the repository
user ~/.claude.json, for all projects Servers you always use, such as playwright

Don't load the same server in two different scopes (see Incident 2).

Check and manage

claude mcp list             # lists the servers and their status
claude mcp get playwright   # details of one server
claude mcp remove jira      # remove a server

Inside a claude session, the /mcp command shows whether each server is Connected, Failed, or Pending approval. Servers from .mcp.json ask for approval the first time. If you answered wrong, you can be asked again by running claude mcp reset-project-choices.


Codex CLI

Codex CLI shares its configuration with the Codex extension and with the ChatGPT desktop app (~/.codex/config.toml).

Add the servers

codex mcp add playwright -- npx -y @playwright/mcp@latest --browser chromium

codex mcp add jira \
  --env JIRA_URL=https://your-site.atlassian.net/ \
  --env JIRA_USERNAME=your.email@company.com \
  --env JIRA_API_TOKEN=<token> \
  --env CONFLUENCE_URL=https://your-site.atlassian.net/wiki \
  --env CONFLUENCE_USERNAME=your.email@company.com \
  --env CONFLUENCE_API_TOKEN=<token> \
  --env READ_ONLY_MODE=true \
  -- uvx mcp-atlassian

codex mcp add azure-devops \
  --env AZURE_DEVOPS_ORG_URL=https://dev.azure.com/your-org \
  --env AZURE_DEVOPS_AUTH_METHOD=pat \
  --env AZURE_DEVOPS_PAT=<token> \
  -- npx -y @tiberriver256/mcp-server-azure-devops

If you prefer to edit the file by hand (for example, to use env_vars and avoid writing the token), the TOML format is in Codex in VS Code.

Check

codex mcp list

Inside a codex session, /mcp shows the connected servers.


GitHub Copilot CLI

Where it's saved

File Scope
~/.copilot/mcp-config.json All your projects
.mcp.json or .github/mcp.json in the repository root That project (it takes priority over the user configuration)

Since Copilot CLI also reads the repository's .mcp.json, the same file that NEO uses with Claude Code can work for Copilot CLI. Try /mcp show playwright first: everything may already be set up.

Add the servers

Inside a copilot session, type /mcp add: a form opens where you enter the name, the command, the arguments, and the environment variables.

Or edit ~/.copilot/mcp-config.json directly. The root key is mcpServers and the type of a local server is "local":

{
  "mcpServers": {
    "playwright": {
      "type": "local",
      "command": "npx",
      "args": ["-y", "@playwright/mcp@latest", "--browser", "chromium"],
      "env": {},
      "tools": ["*"]
    },
    "jira": {
      "type": "local",
      "command": "uvx",
      "args": ["mcp-atlassian"],
      "env": {
        "JIRA_URL": "https://your-site.atlassian.net/",
        "JIRA_USERNAME": "your.email@company.com",
        "JIRA_API_TOKEN": "<token>",
        "READ_ONLY_MODE": "true"
      },
      "tools": ["*"]
    }
  }
}

"tools": ["*"] enables all of the server's tools.

Check

/mcp show playwright

The Copilot CLI configuration is also the one used by the GitHub Copilot desktop app.


Katalon Studio (remote server)

katalon-studio is a remote (HTTP) server published by Katalon Studio: you add it with --transport http and the URL, with no command. Full guide: Set up the Katalon Studio MCP.

# Claude Code CLI
claude mcp add --transport http --scope project katalon-studio \
  http://127.0.0.1:33699/mcp/stream \
  --header "Authorization: Bearer <token>"

# Codex CLI
codex mcp add katalon-studio --url http://127.0.0.1:33699/mcp/stream \
  --bearer-token-env-var KATALON_MCP_TOKEN

Use the URL your Katalon Studio shows. If the server doesn't ask for a token, omit --header / --bearer-token-env-var. For GitHub Copilot CLI, add the block with "type": "http" and "url" to the same configuration file.

Katalon Studio must be open with the suite's project, and the handshake takes ~30 seconds: set MCP_TIMEOUT=60000 before opening the assistant.


Common problems in the terminal

What you see Why it can happen What to do
claude mcp add treats the server's arguments as its own options The -- before the server command is missing Put -- right before npx / uvx
The server ended up in the wrong scope The default scope (local) was used instead of project Remove it with claude mcp remove and add it again with --scope project
The token ended up in the terminal history It was passed with --env on the command line Clear the history, or put the token in the file or in an environment variable
uvx: command not found uv isn't installed Install uv (docs.astral.sh/uv) and open a new terminal