allye-mcp 1.23.2

Allye MCP Server
Python MCP server for Allye Cloud API integration

Quick Start • Installation • Configuration • Structure • Testing

Overview

Allye MCP connects MCP-compatible clients (Claude Code, Cursor, Windsurf, VS Code, etc.) directly to the Allye Cloud APIs. Every tool invocation hits the live backend—no outdated snapshots or hallucinated IDs.

Available Tools:

• kb — Project knowledge base: search, read and write pages by section with revision checks, backlinks, history and restore (use it for project docs)
• skills — Authorized document library: create, read, edit, trash, and revision history
• productivity — Personal TODO management (never shared): scheduling, Today/Upcoming/Someday/Logbook views, checklists, reordering and a link to a spec
• intelligence — Memories and smart operations
• user_config — Deprecated: returns no data (use memory_preferences); removal planned after 30 days in production
• initialize — Session context (user, tenant, teams, open work); include_user_docs is deprecated and ignored
• allye_health_check — Backend health check
• api_catalog — Allye API specifications: search, list and inspect endpoint details
• projects, epics, specs, tasks — Projects module (Project → Epic → Spec → Task)
• team — Default team: team_set_default sets your default team (shared by all your sessions)

See Tools for the skills library and the Projects module.

Quick Start

Remote server with native OAuth (recommended)

Configure the server name allye with the canonical URL:

https://mcp.allye.app/mcp

Use the client's native MCP OAuth flow. Do not configure a fixed Authorization header, PAT, legacy client ID, tenant path, or token helper. The client discovers OAuth from:

https://mcp.allye.app/.well-known/oauth-protected-resource/mcp

Examples:

# Claude Code
claude mcp add --transport http allye https://mcp.allye.app/mcp

# Codex
codex mcp add allye --url https://mcp.allye.app/mcp
codex mcp login allye

For OpenCode, define an enabled remote server named allye at the same URL, then run opencode mcp auth allye. With Pi and pi-mcp-adapter, configure the same name and URL, then use /mcp-auth allye and /mcp reconnect allye. Each installation completes its own browser authorization.

Local STDIO with an explicit PAT

PAT authentication remains supported only for local STDIO:

pipx install allye-mcp
ALLYE_TRANSPORT_MODE=stdio allye-mcp --pat <your-token>

Documentation

Useful Links