Adding your own server

Any MCP server can be added to PandaOS, in three forms, at three scopes.

Three ways to paste it

Add custom server, beside the search box of the integration catalogue (Customize, Integrations, Connect integration), takes a server in whichever form you already have:

• a URL, for a server that runs somewhere else, signed in through your browser or with an API key pair;
• a config snippet from the server's docs: the mcpServers JSON most clients use, Codex's [mcp_servers.name] TOML, or OpenCode's mcp JSON;
• a CLI add command for Claude or Codex, pasted verbatim.

All of them are parsed, and what was understood is shown for you to check before anything is saved. Whichever form it came in, the server is set up for Claude, Codex and OpenCode alike.

Local or remote

A local server is a process PandaOS starts on your machine, and its row carries a terminal icon. A remote server is reached over the network and carries a globe. The status dot reads green for on, grey for off, red for an authentication error and amber while authenticating.

A server that needs authenticating says so, and connects from its row. One can be switched off without being removed.

Three scopes

Where a server is saved decides who gets it:

• Global. Every project on this machine.
• Project, shared. Written into the project's .mcp.json and committed, so everyone on the repository gets it.
• Project, local. This project, this machine, not committed.

PandaOS writes each scope where the harness the project runs on expects to find it, so the same server works whichever engine you switch to.