Where to add the configuration
Prefer the client's own command when one is available. The command writes the expected format and reduces the risk of editing the wrong file. For manual configuration, these are the most common paths on Linux and macOS:
| Client | User configuration | Project configuration |
|---|---|---|
| Codex | ~/.codex/config.toml | <project>/.codex/config.toml |
| Claude Code | ~/.claude.json | <project>/.mcp.json |
| OpenCode | ~/.config/opencode/opencode.json or .jsonc | <project>/opencode.json or <project>/.opencode/opencode.json |
| Pi | ~/.pi/agent/mcp.json or ~/.config/mcp/mcp.json | <project>/.mcp.json or <project>/.pi/mcp.json |
| Hermes Agent | ~/.hermes/config.yaml | — |
~ represents the user's home directory. User configuration is available across projects; project configuration applies only to that directory and can be shared with the team when the client supports it.
In Codex and Claude Code, prefer codex mcp add and claude mcp add to write the configuration. In OpenCode and Pi, edit JSON/JSONC or use the client's own management interface. In Hermes Agent, edit YAML and run hermes mcp login zenifra.
Add only the public URL and the fields shown in this guide. Do not place access tokens, refresh tokens, client secrets, or cookies in these files. Each client stores OAuth credentials through its own authentication flow. On Windows, prefer the client commands and consult its official reference to locate the corresponding file.
Last updated on