AI providers supported by MCPX and their config formats

MCPX translates the single canonical .agents/mcp.json file into 8 different provider-specific configuration formats. Each provider has its own file location, root key, serialization format, and field-naming conventions. You never need to touch these generated files directly — MCPX manages them for you. This page documents exactly what each provider expects so you understand what MCPX produces and why.

Valid provider IDs

The following IDs are accepted in the providers array of the canonical config file:

antigravity-cli
claude-code
copilot-cli
intellij
kimi-cli
openai-codex
opencode
vscode

Provider details

Claude Code

Provider ID: claude-code

Aspect	Detail
Project config	`.mcp.json`
Global config	`~/.claude.json`
Format	JSON
Root key	`mcpServers`
Scope support	Project and global

Field mappings:

Every server entry receives an explicit type field set to "stdio" or "http" matching the canonical transport value.
env maps directly to env.
HTTP servers emit url and optional headers.

Global scope behavior: When writing to the global ~/.claude.json, MCPX merges the mcpServers key into the existing file so that other Claude Code settings (such as preferences) are preserved.Example output (project):

{
  "mcpServers": {
    "github": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    }
  }
}

Antigravity CLI

Provider ID: antigravity-cli

Aspect	Detail
Project config	`.gemini/config/mcp_config.json`
Global config	`~/.gemini/config/mcp_config.json`
Format	JSON
Root key	`mcpServers`
Scope support	Project and global

Field mappings:

Unlike most other providers, Antigravity CLI does not emit a type field.
HTTP servers use serverUrl (not url) for the remote endpoint.
Disabled servers (where enabled: false) are included in the output with disabled: true rather than omitted.
env and headers map directly.

Example output:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    },
    "remote-api": {
      "serverUrl": "https://mcp.example.com",
      "headers": {
        "Authorization": "Bearer sk-xxx"
      }
    }
  }
}

Kimi CLI

Provider ID: kimi-cli

Aspect	Detail
Project config	`.kimi-code/mcp.json`
Global config	`~/.kimi-code/mcp.json`
Format	JSON
Root key	`mcpServers`
Scope support	Project and global

Field mappings:

No type field is emitted.
HTTP servers emit url directly.
env and headers map directly.
Disabled servers are omitted from output entirely.

Global path override: The global config path respects the $KIMI_CODE_HOME environment variable. If KIMI_CODE_HOME is set, MCPX writes the global config to $KIMI_CODE_HOME/mcp.json instead of ~/.kimi-code/mcp.json.Example output:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    }
  }
}

OpenAI Codex

Provider ID: openai-codex

Aspect	Detail
Project config	`.codex/config.toml`
Global config	`~/.codex/config.toml`
Format	TOML
Root key	`mcp_servers`
Scope support	Project and global

Field mappings:

The only provider that uses TOML format instead of JSON.
The root key is mcp_servers (underscore, not camelCase).
HTTP servers emit url and http_headers (not headers).
Disabled servers are omitted.

Smart merge: When a .codex/config.toml already exists, MCPX parses the full file, replaces only the mcp_servers table, and re-serializes it. This preserves any existing Codex settings such as model, approval_mode, and custom instructions.Example output:

[mcp_servers.github]
command = "npx"
args = ["-y", "@anthropic-ai/mcp-github-server"]

[mcp_servers.github.env]
GITHUB_PERSONAL_ACCESS_TOKEN = "ghp_xxx"

OpenCode

Provider ID: opencode

Aspect	Detail
Project config	`opencode.json`
Global config	`~/.config/opencode/opencode.jsonc` (falls back to `~/.config/opencode/opencode.json`)
Format	JSONC (global) / JSON (project)
Root key	`mcp`
Scope support	Project and global

Field mappings:

command and args are merged into a single array under the command key: [command, ...args].
Environment variables are stored under environment (not env).
stdio servers receive type: "local".
HTTP servers receive type: "remote".
The enabled field is written explicitly in every server entry.
The generated file always includes a $schema key pointing to the OpenCode config schema.

Example output (project):

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "github": {
      "enabled": true,
      "type": "local",
      "command": ["npx", "-y", "@anthropic-ai/mcp-github-server"],
      "environment": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    }
  }
}

Copilot CLI

Provider ID: copilot-cli

Aspect	Detail
Project config	`.copilot/mcp-config.json`
Global config	`~/.copilot/mcp-config.json`
Format	JSON
Root key	`mcpServers`
Scope support	Project and global

Field mappings:

Every server entry receives an explicit type field ("stdio" or "http").
Every server entry also receives a tools field defaulted to ["*"], which grants access to all tools exposed by that server.
Disabled servers are omitted.
env and headers map directly.

Example output:

{
  "mcpServers": {
    "github": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      },
      "tools": ["*"]
    }
  }
}

VS Code

Provider ID: vscode

Aspect	Detail
Project config	`.vscode/mcp.json`
Global config	Not supported
Format	JSON
Root key	`servers`
Scope support	Project only

Field mappings:

Root key is servers (not mcpServers).
Every server entry receives an explicit type field.
HTTP transport is mapped to type: "sse" (not "http"), because VS Code uses the SSE transport label for remote servers.
Disabled servers are omitted.
env and headers map directly.

Example output:

{
  "servers": {
    "github": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    },
    "remote-api": {
      "type": "sse",
      "url": "https://mcp.example.com",
      "headers": {
        "Authorization": "Bearer sk-xxx"
      }
    }
  }
}

IntelliJ IDEA

Provider ID: intellij

Aspect	Detail
Project config	`.idea/mcp.json`
Global config	Not supported
Format	JSON
Root key	`mcpServers`
Scope support	Project only

Field mappings:

No type field is emitted. IntelliJ IDEA infers the transport type from the presence of command (stdio) or url (HTTP).
env and headers map directly.
Disabled servers are omitted.

Example output:

{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@anthropic-ai/mcp-github-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_xxx"
      }
    }
  }
}

Summary table

Provider ID	Display Name	Format	Project Config	Global Config
`claude-code`	Claude Code	JSON	`.mcp.json`	`~/.claude.json`
`antigravity-cli`	Antigravity CLI	JSON	`.gemini/config/mcp_config.json`	`~/.gemini/config/mcp_config.json`
`kimi-cli`	Kimi CLI	JSON	`.kimi-code/mcp.json`	`~/.kimi-code/mcp.json`
`openai-codex`	OpenAI Codex	TOML	`.codex/config.toml`	`~/.codex/config.toml`
`opencode`	OpenCode	JSONC/JSON	`opencode.json`	`~/.config/opencode/opencode.jsonc`
`copilot-cli`	Copilot CLI	JSON	`.copilot/mcp-config.json`	`~/.copilot/mcp-config.json`
`vscode`	VS Code	JSON	`.vscode/mcp.json`	Not supported
`intellij`	IntelliJ IDEA	JSON	`.idea/mcp.json`	Not supported

When a provider is removed from the providers array and mcpx sync is run, MCPX deletes that provider’s config file for the active scope. Make sure the file is not checked in anywhere critical before removing a provider, or commit the deletion intentionally.

Get Started

Command Reference

Configuration

Guides

AI providers supported by MCPX and their config formats

Valid provider IDs

Provider details

Summary table

Build docs developers (and LLMs) love

Get Started

Command Reference

Configuration

Guides

Documentation Index

​Valid provider IDs

​Provider details

​Summary table

Build docs developers (and LLMs) love

Valid provider IDs

Provider details

Summary table