SkillFoxx

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

  • 0 ★ on the repository
  • Last commit
  • Apache-2.0
MCP server

Broad access

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
All reasons and checks
Russian stack

sparko161-droid/pyrus_mcp_bd_complectAuthor:sparko161-droid

Install

Services

Manual install

cd pyrus_mcp_server && uv sync

Installation inside the server subfolder after cloning the whole repository.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • 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

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 deadlines

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.

Limitations

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.

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.

Discussion

No questions or reviews yet.

All Pyrus tools

Pyrus API MCP server

Pyrus API MCP Server

Russian stack

An MCP server for Pyrus with multi-account support: inbox, tasks, forms and registries, contacts, announcements and calendar

MCP serverExtended access
Russian stack

A Pyrus MCP server built on the official pyrus-api library: 41 API methods and three access tiers that hide disallowed tools

MCP serverExtended access
Russian stack

An MCP server for the iikoServer REST API: products, employees, invoices, cash shifts, encashment and OLAP reports, including raw calls to any endpoint

MCP serverBroad access1
Russian stack

iikoServer REST API MCP server: menu items, staff, invoices, cash shifts, OLAP reports and revenue by venue

MCP serverBroad access3
Russian stack

A lightweight MCP server for manually debugging the iikoTransport API (api-ru.iiko.services) with v2 authorization and a universal arbitrary-request tool

MCP serverExtended access1

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.

README badge

Report a problem