Multi-tenant Pyrus MCP server
Pyrus AI Ecosystem — MCP Infrastructure
An enterprise Pyrus v4 API MCP server with multi-tenancy, SQLite persistence and metrics, inside a larger monorepo
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Writes and changes tasks and data in the live Pyrus account across several tenants
- Stores credentials and a call audit trail in its own database accessible to the server
Install
Manual install
cd pyrus_mcp_server && uv syncInstallation inside the server subfolder after cloning the whole repository.
This is third-party code. Review the repository files before installing.
What it does
Inside a larger monorepo sits a working pyrus_mcp_server built on FastMCP: it gives an agent access to Pyrus tasks, forms, members, directories and the knowledge base, logs an audit trail of tool calls, persists state in SQLite and exposes Prometheus metrics. It has role-based authorization, Pyrus webhook handling and a separate test suite including load and security tests. The same repository also holds a companion iiko_mcp server for the iiko point-of-sale system and extensive architecture material specific to one company and its own clients.
Who it is for. For teams willing to navigate a large monorepo in exchange for a mature, multi-tenant Pyrus MCP server with observability and tests.
Good fit when
- You need a Pyrus MCP server with multiple tenants and a call audit log
- You need Prometheus metrics and Pyrus webhook handling out of the box
- You also want an iiko MCP server alongside Pyrus
Not a fit when
- You are not willing to navigate a large monorepo for one subfolder
- You need a published package: the server only installs from source
- You are uncomfortable with the repository containing the author company's own client-specific material
Example request
Find all open Pyrus tasks for my account and show their deadlinesLimitations
The repository is a 750+ file monorepo containing the author company's own client-specific material (bots, forms, scripts named after real clients), not only a reusable server. The pyrus_mcp_server subfolder's own README is empty; documentation exists only at the top level and describes the project as infrastructure under development rather than a finished product. The package is not published anywhere; installation is only via cloning and uv sync inside the pyrus_mcp_server subfolder. The repository has node_modules committed.
How to disable. Stop the server container or process and remove it from your MCP client configuration.
MCP
- Transport
- stdio, http
- Authentication
- API key
| Environment variables | |
|---|---|
| PYRUS_LOGIN required | The email used to sign into Pyrus API v4. |
| PYRUS_SECURITY_KEY required, secret | The Pyrus API v4 secret key. |
| PYRUS_WEBHOOK_SECRET secret | The secret used to verify incoming Pyrus webhooks. |
Security check
- Writes and changes tasks and data in the live Pyrus account across several tenants
- Stores credentials and a call audit trail in its own database accessible to the server
README in short
The top-level README describes the repository as the home for Pyrus MCP infrastructure and a future Knowledge MCP, with a product-boundary diagram and a list of normative documents like IMPLEMENTATION_PLAN.md. pyrus_mcp_server itself has no README of its own, but its pyproject.toml describes it as an enterprise FastMCP server for the Pyrus v4 API with multi-tenancy, SQLite persistence and observability, and its .env.example and docker-compose.yml show a real working setup.
FAQ
Is this a ready-to-use product?
The top-level README calls the project infrastructure under development and lists pyrus_mcp_server readiness as the top priority, not a finished release.
Do I need access to the whole repository?
Running the server only requires the pyrus_mcp_server subfolder; the rest (client bots, Knowledge MCP) can be ignored.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail