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 historyproductivity— TODO managementintelligence— Memories and smart operationsuser_config— User configuration documentsinitialize— Personalized setupallye_health_check— Backend health checkapi_catalog— Allye API specifications: search, list and inspect endpoint detailsprojects,epics,specs,tasks— Projects module (Project → Epic → Spec → Task)team— Default team:team_set_defaultsets 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
| Topic | File |
|---|---|
| Tools: skills library, Projects module | docs/tools.md |
| Requirements and installation | docs/installation.md |
| Configuration: STDIO, environment variables, HTTP | docs/configuration.md |
| Project structure and tech stack | docs/project-structure.md |
| Development, commit convention, CI/CD | docs/development.md |
| Troubleshooting | docs/troubleshooting.md |
| Security | docs/security.md |
| Testing | TESTING.md |
| MCP action → API mapping | docs/testing/mcp_action_matrix.md |
Useful Links
| Resource | URL |
|---|---|
| PyPI | https://pypi.org/project/allye-mcp/ |
| Allye Cloud | https://allye.devshire.app |
| MCP Protocol | https://modelcontextprotocol.io |
Metadata
Release files for allye-mcp 1.19.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| allye_mcp-1.19.0.tar.gz | 168.1 kB | Without provenance | Details for allye_mcp-1.19.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| allye_mcp-1.19.0-py3-none-any.whl | Python 3 | none | any | Details for allye_mcp-1.19.0-py3-none-any.whl |
Total release size: 370.6 kB
Release files / allye_mcp-1.19.0.tar.gz
| Download URL | allye_mcp-1.19.0.tar.gz |
|---|---|
| Size | 168.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6a526abcd0d0be9d22dd9793378a9200e6f828dd592ac2883a6da6a0eeb1a4c
|
|
BLAKE2b-256 checksum How to use checksums |
cad4c6a51c3c0bcfc9b62d1f0f0c14059f882d4350c82120a043977434b76db8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Release files / allye_mcp-1.19.0-py3-none-any.whl
| Download URL | allye_mcp-1.19.0-py3-none-any.whl |
|---|---|
| Size | 202.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f19a628daedb671a026c7028774261f6888ea54d66ff0cd3b15d9675e0831df
|
|
BLAKE2b-256 checksum How to use checksums |
b70de1bd6f509f3c7ed3dea261047e276c0583975a44e6e82e389b644a236f7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.17
|
Security for allye-mcp 1.19.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.