Pyrus MCP server with access tiers

pyrus-mcp

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

  • 0 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

  • In modes above read-only it can create and change tasks in the live Pyrus account
  • The security key grants access to all account data within its permissions
All reasons and checks
Russian stack

brain-boost-academy/pyrus-mcp

Install

Services

Manual install

uvx --from git+https://github.com/brain-boost-academy/pyrus-mcp pyrus-mcp

The consumer install method from the README.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • In modes above read-only it can create and change tasks in the live Pyrus account
  • The security key grants access to all account data within its permissions

This is third-party code. Review the repository files before installing.

What it does

The server wraps the official pyrus-api library and gives an agent access to all 41 Pyrus API methods over stdio. The key feature: filtering happens when tools are registered, not at request time. If the access mode disallows a method, it is simply absent from the tool list, so the agent cannot call it even by accident. Three tiers are available, from read-only to full control, set by an environment variable at startup.

Who it is for. For teams that care about limiting exactly what an agent can do in Pyrus, rather than relying on its care at runtime.

Good fit when

  • You need full coverage of the official Pyrus API methods, not just tasks
  • You need to reliably hide dangerous operations from the agent rather than just warn it
  • Non-commercial use under the PolyForm Strict license works for you

Not a fit when

  • You need commercial use, source modification or redistribution: the PolyForm Strict 1.0.0 license forbids this outside the listed organization categories
  • You do not have Python 3.14: the server specifically requires it

Example request

Connect Pyrus in read-only mode and show all my open tasks

MCP

Transport
stdio
Authentication
API key

Environment variables

PYRUS_LOGIN required
The Pyrus login email.
PYRUS_SECURITY_KEY required, secret
The Pyrus security key.
PYRUS_MCP_MODE
The server's access tier, non-destructive by default.

Limitations

The PolyForm Strict 1.0.0 license only allows non-commercial use with no source modification or redistribution, except for the listed organization categories such as charities, education and government. A different mode requires a separate arrangement with the rights holder. Python 3.14 is required. Installing via uvx --from git+ re-resolves dependencies without consulting uv.lock, so the upper version bounds in pyproject.toml matter.

How to disable. Stop the server process and remove it from your MCP client configuration.

FAQ

How do I limit the agent to read-only?

Keep the default non-destructive mode or set PYRUS_MCP_MODE explicitly; disallowed methods never appear in tools/list.

Can the server be used in a commercial product?

No, the PolyForm Strict 1.0.0 license forbids that, except for specific non-commercial and government organization categories.

Discussion

No questions or reviews yet.

Multi-tenant Pyrus MCP server

Pyrus AI Ecosystem — MCP Infrastructure

Russian stack

An enterprise Pyrus v4 API MCP server with multi-tenancy, SQLite persistence and metrics, inside a larger monorepo

MCP serverBroad access

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 compact FastMCP-based MCP server with 21 tools for AmoCRM: contacts, deals, tasks, notes, tags and pipelines in a single server.py

MCP serverBroad access
Russian stack

An MCP server covering all seventeen Wildberries Seller API hosts: sales, stock, product cards, prices, financial reports and reviews

MCP serverBroad access4Repository stars
Russian stack

An MCP server for the Ozon Seller API with a catalog of 441 methods, read and write access classes, and keys stored outside the repository

MCP serverBroad access3Repository stars
Russian stack

A PyPI-published Planfix MCP server: 15 tools for tasks, contacts, projects and directories, plus webhook intake

MCP serverExtended access

README in short

The Russian README explains the security model in detail: tools are filtered at registration time rather than at runtime, so a disallowed method is unavailable to the model in principle. It states the PolyForm Strict 1.0.0 license with its list of allowed organization categories, an environment-variable table (PYRUS_LOGIN, PYRUS_SECURITY_KEY, PYRUS_PERSON_ID, PYRUS_ACCESS_TOKEN, PYRUS_MCP_MODE), and a warning about dependency resolution when installing via uvx --from git+.

README badge

Report a problem