SkillFoxx

Planfix MCP server

Planfix MCP Server

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

  • 11 ★ on the repository
  • Last commit
MCP server

Extended access

Why this level

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

popstas/planfix-mcp-serverAuthor:popstas

Install

Services

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/planfix-mcp-server

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

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

  • Creates and changes leads, tasks, contacts and companies in the live Planfix account
  • The API token 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 gives an agent tools for Planfix: creating and searching leads with conversion to tasks, managing contacts and companies, creating tasks and comments, generating reports, and an arbitrary planfix_request call to any REST API v2.0 method. Planfix custom fields, such as email, phone, Telegram, manager or lead source, are configured via environment variables or a config.yml file, which can be pointed at separately per account. There is a separate SSE server, HTTP proxy support for all requests, and an optional integration with Planfix's Chat API to create tasks from conversations.

Who it is for. For sales teams and developers running leads and tasks in Planfix who want to manage them through an agent.

Good fit when

  • You need to create a lead or task in Planfix from an agent conversation
  • You need to map Planfix custom fields (email, phone, manager) to agent tools
  • You need one server covering several Planfix accounts via config.yml

Not a fit when

  • You run a regional .ru Planfix install without setting PLANFIX_BASE_URL: the server defaults to .planfix.com
  • You do not want to deal with custom fields: without them some tools (lead creation, email search) work only partially

Example request

Create a lead in Planfix for this client and convert it into a task with a comment about the first call

MCP

Transport
stdio, sse
Authentication
API key

Environment variables

PLANFIX_ACCOUNT required
Planfix account name, for example yourcompany.
PLANFIX_TOKEN required, secret
Planfix API token with the necessary permissions.
PLANFIX_BASE_URL
REST API base URL for regional installs, for example .planfix.ru.

Limitations

Some functionality depends on custom fields that need to be created in Planfix itself and their IDs listed in the config. Planfix's system field for additional email addresses is read-only over the REST API, so new addresses are written to a separate custom field you have to create yourself. Regional installs (.ru and others) need PLANFIX_BASE_URL set explicitly, otherwise the server talks to .planfix.com.

How to disable. Remove the server from your MCP client config, for example claude mcp remove planfix in Claude Code.

FAQ

How do I set up several Planfix accounts?

With a separate config file for each: the PLANFIX_CONFIG variable points to the path, and PLANFIX_ACCOUNT overrides the account for that run.

Can I call an arbitrary API method?

Yes, the planfix_request tool calls any Planfix REST API v2.0 method directly.

Discussion

No questions or reviews yet.

All Planfix tools

Planfix MCP

planfix-mcp

Russian stack

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

MCP serverBroad access5

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

An unofficial Planfix MCP server with 93 read operations via the web client interface: tasks, comments, webhooks, integrations

MCP serverBroad access3
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 English README describes the Planfix integration via REST API v2.0 with Bearer token auth, gives a full list of environment variables for custom fields with notes on the system versus custom additional-email field, a config.yml example with leadTaskFields, contactFields and userFields, and a Chat API integration block for creating tasks from conversations.

README badge

Report a problem