Installation & Setup
Connect Pi, Claude Code, Codex, OpenCode or OMP to the Allye remote MCP server with OAuth 2.1.
Allye is a remote MCP server. There is nothing to install for the connection itself and no token to create: your agent connects to one URL and you sign in through OAuth 2.1 in the browser.
https://mcp.allye.app/mcpPrerequisites
- An alpha invitation to Allye (join the waitlist at allye.app). Sign in at allye.app/hq.
- One of the supported harnesses: Pi, Claude Code, Codex, OpenCode or OMP.
How the connection works
- Add the MCP URL to your harness, either through its plugin or its MCP configuration.
- Start the harness. It opens the OAuth 2.1 sign-in in your browser.
- Approve access. The harness stores the authorization and reconnects on its own.
The steps for adding the URL differ by harness. Each section below links to the guide that owns those steps.
Pi
Pi is the recommended harness, because it gives you the most freedom to choose and configure how the agent works. Follow the Pi install guide.
Claude Code
Claude Code uses the Allye plugin, which handles the OAuth sign-in for you and adds the Allye skills and subagents. See the Allye plugin page.
Codex
Follow the Codex install guide.
OpenCode
Follow the OpenCode install guide.
OMP
OMP is supported over the same URL, https://mcp.allye.app/mcp, with the same OAuth 2.1 sign-in. See the OMP install guide.
Verify
Ask your agent to initialize Allye. The response should show your user, your tenant and your teams. If it does not, repeat the sign-in from your harness and check that the URL above is the one configured.
Next
- Actions reference for what the MCP server exposes.
- Install guides for every harness in one place.