MCP servers

One definition, generated as JSON, TOML or YAML per target agent — with a diff before anything is written.

Updated · 2026-11-02

Every agent spells MCP configuration differently. AgentHub lets you maintain one definition and generate the rest.

Format matrix

Target	File	Format
Claude Code / CodeBuddy / Gemini	`mcp.json` and friends	JSON
Codex	`~/.codex/config.toml`	TOML
Hermes	`~/.hermes/config.yaml`	YAML

Adding a server means filling in the command, arguments and environment once; the UI previews every format.

Write flow

Add or edit a definition in the list.
Choose “Generate write plan” — the drawer shows a per-file diff.
Confirm row by row, then apply. Backups happen before writing.

Scope

An MCP definition can be global, or scoped to a single project:

agenthub mcp import ./mcp.json --project ~/Code/my-app

The desktop app can switch scope from the top bar; the list then narrows to the current scope. Project-scoped definitions live in .agenthub/project.json and travel with the repository.

Common questions

Does editing a definition affect a running agent?

No. Config files are read on startup, so live sessions keep their current settings. New sessions pick up the change.

Can I edit the raw files directly?

Yes, but that bypasses plans and backups. At minimum, route those edits through a plan so you have a batch to roll back to.