Invite a friend, get 1 month of Pro freeHow it works

Manage MCP servers in one place

Instead of juggling each CLI’s MCP config file, add servers to AgentVera once. Registered servers (stdio, HTTP and SSE) connect when agents start: to all agents, the ones you choose, a group’s agents or a team role. Agents can also attach the servers they need themselves.

A ready-made catalog

On the MCP page (⌘⌥M), “+” lists 23 ready servers by category.

  • Browser: Playwright, Chrome DevTools.
  • Docs: Context7, Cloudflare Docs.
  • Development: GitHub, Git, Sentry.
  • Mobile: Mobile MCP, MobileBuildMCP, iOS Simulator, Firebase.
  • Data and memory: Filesystem, Memory, Fetch, Sequential Thinking, Supabase.
  • Product and team: Linear, Notion, Stripe. Design: Figma, Canva.
  • Marketing and media: fal.ai, Meta Ads.

Test it, see the cost

A connection test lists the server’s tools, prompts and resources and an approximate token cost per tool, so you know how much context a server adds to every request. Secret environment variables and headers are kept in your operating system’s keychain, and servers can be limited to certain projects.

In every CLI agent, remote servers included

MCP servers go to every CLI agent that takes them: besides Claude Code and Codex, that’s opencode, Copilot, Qwen Code, Goose, Amp, Cursor, Antigravity, Gemini, Droid, Kimi, Vibe, Crush, Kiro, Cline and Hermes. Remote servers go through AgentVera’s gateway.

  • Sign in once in the app to a remote server that needs OAuth; every agent uses that sign-in.
  • The agent’s CLI holds no header or token; the gateway connects to the remote server.
  • Groups and team roles have their own MCP servers; every agent in the group or role starts with them.

Agents ask for servers themselves

An agent with AgentVera’s agent tools lists the registered MCP servers and attaches one to itself or to an agent of its group, no approval needed. If it needs a server that isn’t there yet, it asks: you approve it in the app, the server is added to the project, tested and attached to the agent, and a sign-in window opens if the remote server needs OAuth. The agent restarts with the same conversation when its turn ends, with the new tools ready.

In step with your CLIs, plus a shared board

Servers from Claude Code’s and Codex’s own settings are listed with their health; import them into AgentVera or remove them from the CLI. AgentVera’s servers can be written to the CLI settings too. Each project also gets a shared board server (agentvera-board): agents post notes, decisions, todos and findings, and you read them in the Board tab of the right panel.

Questions

Which agents do MCP servers connect to?

Every CLI agent that takes MCP: Claude Code, Codex, opencode, Copilot, Qwen Code, Goose, Amp, Cursor, Antigravity, Gemini, Droid, Kimi, Vibe, Crush, Kiro, Cline and Hermes. Aider takes no MCP. Add each server to all agents, the ones you pick, a group or a team role.

Can an agent add a new MCP server on its own?

It can attach a registered server to itself or to an agent of its group without approval. A new server is only added when you approve it in the app.

Where are secrets stored?

In your operating system’s keychain. They’re left out of settings backups too.

How do I see a server’s token cost?

After a connection test, the tools list shows an approximate token cost for each tool.

What is the shared board?

A notice board shared by the project’s agents and you. Agents read and write it through MCP tools; entries are stored locally.

Related features

Related terms:MCP (Model Context Protocol)

All featuresSee the 18 supported coding agents

Bring your agents to one desk.

Start on the free plan. Download it, add a project folder and open your first agent.