Getting Started

Connect your AI agent to Allye through the remote MCP server.

Allye is a shared workspace for projects, specs, tasks, docs and memory that your AI agents can reach over MCP. Your agent reads the same project context your team works from, instead of starting every session from zero.

Allye is an invitation-only alpha: join the waitlist and we email you an access link. Teams and Enterprise plans are coming soon.

What you get

Feature	What it does
Projects	Project > Epic > Spec > Task, with keys like `KEY-N` for specs and `KEY-N.M` for tasks
Knowledge base	Pages your team and your agents read and write, linked to specs
Memories	Context persists across AI sessions, so agents remember your decisions
Skills	Reusable instructions and workflows your agents can load
Bridge	The Allye plugin crew that runs specs end to end through specialized agents

Choose your path

Web app

Go to allye.app/hq
Sign in with your alpha invitation
Create a project and your first spec

Connect your agent

Allye is a remote MCP server. There is nothing to run locally:

https://mcp.allye.app/mcp

Your harness opens an OAuth 2.1 consent in the browser the first time it connects. Supported harnesses are Claude Code, Codex, OpenCode, Pi and OMP. Pick yours in the install guides or read the MCP installation guide.

Core concepts

Project hierarchy

Project
└── Epic
    └── Spec
        └── Task

A project groups epics. An epic groups specs. A spec holds the rules and acceptance criteria and is addressed as KEY-N. A task is a small unit of work inside a spec, addressed as KEY-N.M.

Memories

Context saved by you or your agents. When you save a decision, your agents can retrieve it in future sessions and avoid re-asking or contradicting past choices.

Knowledge base

Pages for company, project and personal knowledge. Agents search it for context before they write code.

Quick example

Once your agent is connected (illustrative transcript):

> what is blocking ALY-12?

agent: reading spec ALY-12, its tasks and saved memories
  ALY-12.3 is waiting on ALY-12.2
  decision on record: keep SSO on the same domain