SkillFoxx

Type a name, a task or a service

Pyrus MCP server on npm

Pyrus MCP Server

An npm-published Pyrus MCP server: tasks, lists, comments and the user profile, installed in one command

MCP server

Medium risk

We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.

Why this level

  • Creates, changes and moves tasks in the live Pyrus account
  • The API token grants access to all account data within its permissions
All reasons and checks
Russian stack

staners2/pyrus-mcpAuthor:staners2

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/pyrus-mcp-server

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

Run in a terminal

claude mcp add --transport stdio --env 'PYRUS_LOGIN=<PYRUS_LOGIN value>' --env 'PYRUS_API_TOKEN=<your PYRUS_API_TOKEN>' pyrus -- npx

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"pyrus","type":"stdio","command":"npx","args":[],"env":{"PYRUS_LOGIN":"<PYRUS_LOGIN value>","PYRUS_API_TOKEN":"<your PYRUS_API_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "pyrus": {
      "type": "stdio",
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add pyrus --env 'PYRUS_LOGIN=<PYRUS_LOGIN value>' --env 'PYRUS_API_TOKEN=<your PYRUS_API_TOKEN>' -- npx

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.pyrus]
command = "npx"
args = []
env = { PYRUS_LOGIN = "<PYRUS_LOGIN value>", PYRUS_API_TOKEN = "<your PYRUS_API_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

gemini mcp add -s user -e 'PYRUS_LOGIN=<PYRUS_LOGIN value>' -e 'PYRUS_API_TOKEN=<your PYRUS_API_TOKEN>' pyrus npx

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "pyrus": {
      "type": "local",
      "command": [
        "npx"
      ],
      "environment": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "pyrus": {
      "command": "npx",
      "args": [],
      "env": {
        "PYRUS_LOGIN": "<PYRUS_LOGIN value>",
        "PYRUS_API_TOKEN": "<your PYRUS_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PYRUS_LOGINrequired
Your Pyrus login email
PYRUS_API_TOKENsecret, required
Your Pyrus API security key

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 71d9741.

Text for your agent

Install the package with npm install -g pyrus-mcp, set PYRUS_LOGIN and PYRUS_API_TOKEN, and add the server with claude mcp add pyrus npx pyrus-mcp using those environment variables.

Other ways from the author
npm install -g pyrus-mcp

Installing the package from npm.

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

What it does

The server gives an agent tools for Pyrus tasks: creating, reading, updating and moving them between lists, finding lists by name, fetching filtered list tasks and related tasks, adding and reading comments, and getting the current user's profile. It is written in TypeScript and published as an npm package, so it installs globally without cloning the repository.

Who it is for. For Pyrus teams that want a ready npm package for basic task operations without building from source.

Good fit when

  • You need a Pyrus MCP server installable with npm install -g
  • You need operations on tasks, lists and comments
  • You need the current user's profile to personalize agent responses

Not a fit when

  • You need forms, catalogs or extended Pyrus knowledge-base access: the server does not cover them
  • You need tiered access control over operations: this server does not have it

Example request

Show my tasks in the Pyrus Inbox list and add a comment to the oldest one

Limitations

The project has a single author with no known wide community, and there are no GitHub releases. The README does not describe working with Pyrus forms and catalogs, only tasks, lists and comments. Pyrus credentials are passed via environment variables with no built-in per-operation access tiers.

How to disable. Remove the server from your MCP client configuration, for example claude mcp remove pyrus.

MCP

Transport
stdio
Authentication
API key
Environment variables
PYRUS_LOGIN
required		The email used to sign into Pyrus.
PYRUS_API_TOKEN
required, secret		The Pyrus API security key.

Security check

  • Creates, changes and moves tasks in the live Pyrus account
  • The API token grants access to all account data within its permissions

README in short

The English README describes installing via npm install -g, configuring PYRUS_LOGIN and PYRUS_API_TOKEN, and connecting to Claude with claude mcp add. Tools are grouped into tasks, lists, comments and the user profile, with links to separate publishing, development and API documents.

FAQ

How do I get a Pyrus token?

Log into Pyrus, open Settings, Integrations, API, and generate a new security key.

Are Pyrus forms supported?

No, the README only covers tasks, lists, comments and the user profile.

Official

Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent

MCP serverHigh risk483
Official

Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex

PluginHigh riskRussian stackNo VPN needed28
Editors’ pick

Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit

MCP serverHigh riskRussian stackNo VPN needed

Bitrix24 portal MCP server

MCP-сервер портала Битрикс24

Official

Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail

MCP serverHigh riskRussian stackNo VPN needed
Foxx AIPyrus MCP server on npm

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.