Connect to Allye MCP

Allye MCP is a hosted remote service. This guide explains how to connect an MCP-compatible AI client; it does not install an MCP server. Platform-specific Allye installation is covered in the Plugin Installation guide.

Prerequisites

• an Allye account with access to the workspace you want to use;
• an MCP-compatible AI client or host agent;
• the remote Allye MCP URL: https://mcp.allye.app.

Connect the remote service

1. Open the host agent's remote MCP connection settings.
2. Enter https://mcp.allye.app as the remote MCP URL.
3. Choose OAuth as the authentication method.
4. Complete sign-in and consent in the browser opened by the host.
5. Return to the host and reconnect Allye MCP if requested.

The host manages the OAuth session and refreshes it when necessary. Do not copy access tokens into prompts, source files, or shared instructions.

Authentication policy

OAuth is the only public authentication method for Allye MCP. Personal Access Tokens (PATs) are not supported for MCP authentication.

Platform installation

The Allye Plugin provides the installation and connection steps for supported platforms, including Claude Code, OpenCode, Cursor, Codex, Gemini CLI, Hermes Agent, and Pi. Start with the Plugin Installation guide, then follow the instructions for your host.

Select a team after connecting

The first MCP protocol initialize exchange automatically loads the authenticated user's context and available teams. This is a protocol step performed by the client; it is not the same as the functional initialize tool described in the Actions Reference.

If the user belongs to multiple teams:

1. call team with action: "team_list";
2. call team with action: "team_switch" and a team name, prefix, or ID;
3. then use team-scoped tools such as work_items, docs, sprints, and boards.

Allye does not automatically select the first team for a multi-team user. Some read operations can run without an active team, but team-scoped writes may require one.

Verify the connection

After OAuth completes, ask the agent to:

1. list the available Allye tools;
2. run allye_health_check;
3. run team with action: "team_current" or team_list;
4. run initialize with action: "init" only if an explicit functional refresh is needed.

A healthy connection exposes the Allye capabilities described in the Actions Reference. allye_health_check is called directly and does not take an action field.