Docs › Loops
Servers
Your own MCP servers for Claude Code, Codex and GitHub Copilot, and how each is doing in a loop.
Where Settings › Loops › Servers
1 min read
How it works
- Open Settings, then Loops, and choose Add server from the Servers heading's menu.
- Give it a name, then pick what it Runs as: a Command, with its Environment, or a URL, with its Headers.
- Pick the agents that get it. Every loop of those agents has it straight away, open ones included.
- In a loop, Loop context at the foot of the message box lists its servers with their state, such as Connected, Needs sign-in or Failed, and their tools.
- A server's row offers what it needs, such as Sign in or Reconnect. Right-click it to Turn off, Sign out or Edit in settings.
Good to know
- When a server is down, the top of the message box says "A server needs attention". Closed, it stays hidden in every loop until that server is up again.
- A server that signs in asks the first time a loop starts it, in your browser.
- Servers are kept in each agent's own files in your home folder, and Origami keeps no copy. The list shows your own, not a project's.
- Codex only takes a server over streamable HTTP.
- Origami's own server is set up under MCP server.