SkillFoxx

Kotelkin Planfix MCP

An MCP server for Planfix over STDIO: 58 tools for tasks, comments, checklists, projects and directories via the REST API

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Tools create and change tasks, comments, projects and custom fields in a Planfix workspace
  • The README advises testing on a separate account where test records are safe to create
All reasons and checks
Russian stack

andreisvetvit/kotelkin-planfix-mcpAuthor:AndreiSVetvit

Install

Services

Manual install

python -m pip install -e .

Install from source after cloning the repository.

Access and checks

How we review

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

  • Tools create and change tasks, comments, projects and custom fields in a Planfix workspace
  • The README advises testing on a separate account where test records are safe to create

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

What it does

A Python server connects Planfix to an MCP client over STDIO with no separate web server, exposing 58 tools on top of the Planfix REST API: creating and searching tasks, changing due dates, statuses and assignees, comments and actions, checklists, DataTags, projects and their templates, directories, processes and objects, custom fields. Authorization uses a Planfix bearer token, which can be kept in the OS keyring via a dedicated command instead of environment variables. It ships local checks that do not call Planfix, a live comparison against the official Swagger spec, and live QA on a test account; config-changing operations like creating custom fields are gated behind a separate flag.

Who it is for. For Planfix users who want to run tasks, comments and directories through an agent instead of the manual interface.

Good fit when

  • You want to create and update Planfix tasks from a chat with an agent
  • You need to work with directories, checklists and DataTags via MCP
  • You want to verify your credentials and Swagger alignment before production use

Not a fit when

  • You need a ready npm or PyPI package: it only installs from source
  • The author still treats the repo as a staging candidate for release, so interface stability is not guaranteed
  • You need bulk changes with no risk to your workspace: some tools write data, so test on a separate account

Example request

Create a Planfix task to review the quarterly report due by Friday and assign it to me

MCP

Transport
stdio
Authentication
API key

Environment variables

PLANFIX_BASE_URL required
REST API address like https://your-company.planfix.com/rest
PLANFIX_TOKEN required, secret
Planfix REST API bearer token

Limitations

The author marks the project a private public-candidate, and going public remains a maintainer decision pending final review. It installs only from source via pip install -e, with no package in a registry. Some tools change Planfix data, and the README explicitly advises testing on an account where test records are safe to create.

How to disable. Remove the kotelkin-planfix-mcp entry from your MCP client config and delete the PLANFIX_TOKEN from your environment or keyring.

FAQ

Where do I get PLANFIX_TOKEN?

A Planfix REST API bearer token from account settings; the README links to the official Planfix REST API docs.

Can I avoid storing the token in environment variables?

Yes, the planfix-mcp-secrets-init command saves the token in the OS keyring instead of .env or the client config.

Discussion

No questions or reviews yet.

All Planfix tools

Planfix MCP server

Planfix MCP Server

Russian stack

An MCP server for Planfix built on REST API v2.0: leads, tasks, contacts, companies, reports and custom fields via config

MCP serverExtended access11

Compact Planfix MCP server

Planfix MCP Server

Russian stack

A lightweight TypeScript Planfix MCP server for tasks: cards, filtered lists, creation, updates, comments and files

MCP serverExtended access
Russian stack

A Python Planfix MCP server: tasks, projects, contacts and reports, plus ready MCP resources and planning prompts

MCP serverExtended access1
Russian stack

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

MCP serverExtended access

Planfix MCP

planfix-mcp

Russian stack

Planfix MCP server: tasks, projects, contacts, comments and employees through the REST API

MCP serverBroad access5

README in short

The Russian and English README describes 58 MCP tools on top of the Planfix REST API, the Python 3.12+ and token requirements, installing via pip install -e, running planfix-mcp-server, and a set of verification commands: a smoke test with no Planfix calls, a Swagger alignment check, a preflight against real credentials, and live QA on a test account with a separate flag for config-changing writes. A security section asks not to commit tokens and to test destructive operations on a non-production workspace.

README badge

Report a problem