Compact Planfix MCP server
Planfix MCP Server
A lightweight TypeScript Planfix MCP server for tasks: cards, filtered lists, creation, updates, comments and files
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 and changes tasks, comments and files in the live Planfix account
- The REST API token grants access to all account data within its permissions
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/kitsukata-planfix-mcpDetects 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 'PLANFIX_BASE_URL=<PLANFIX_BASE_URL value>' --env 'PLANFIX_TOKEN=<your PLANFIX_TOKEN>' planfix -- npx tsx src/index.tsOr add to the file .mcp.json, in the project
{
"mcpServers": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
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":"planfix","type":"stdio","command":"npx","args":["tsx","src/index.ts"],"env":{"PLANFIX_BASE_URL":"<PLANFIX_BASE_URL value>","PLANFIX_TOKEN":"<your PLANFIX_TOKEN>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"planfix": {
"type": "stdio",
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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 planfix --env 'PLANFIX_BASE_URL=<PLANFIX_BASE_URL value>' --env 'PLANFIX_TOKEN=<your PLANFIX_TOKEN>' -- npx tsx src/index.tsOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.planfix]
command = "npx"
args = ["tsx", "src/index.ts"]
env = { PLANFIX_BASE_URL = "<PLANFIX_BASE_URL value>", PLANFIX_TOKEN = "<your PLANFIX_TOKEN>" }If the file already exists, append the block to the end.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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 'PLANFIX_BASE_URL=<PLANFIX_BASE_URL value>' -e 'PLANFIX_TOKEN=<your PLANFIX_TOKEN>' planfix npx tsx src/index.tsOr add to the file ~/.gemini/settings.json, for all projects
{
"mcpServers": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"type": "local",
"command": [
"npx",
"tsx",
"src/index.ts"
],
"environment": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
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": {
"planfix": {
"command": "npx",
"args": [
"tsx",
"src/index.ts"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_TOKEN": "<your PLANFIX_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- URL аккаунта Planfix, например https://your-account.planfix.ru
PLANFIX_TOKENsecret, required- Токен REST API Planfix
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Clone the repository, run npm install, set PLANFIX_BASE_URL and PLANFIX_TOKEN in .env, and start the server with npm run start.
Other ways from the author
npm install && npm run startInstall and run from source after configuring .env.
This is third-party code. Review the repository files before installing.
What it does
The server provides ten tools for working with Planfix tasks over the REST API: an availability check, getting a task by number, a filtered and paginated task list, creating and updating tasks, listing task filters and templates, task comments and files, and a list of processes. The project is compact, with no leads, contacts or reports, just tasks.
Who it is for. For small teams that only need task operations from Planfix and want a lightweight server without extras.
Good fit when
- You need a simple server for Planfix tasks only, without leads and contacts
- You need a TypeScript project with a straightforward npm build
- You need task filters, templates and files
Not a fit when
- You need leads, contacts or reports: the server does not support them
- You need an already published npm package: it builds from source
Example request
Find Planfix task number 1245 and add a comment about the payment statusLimitations
The project is small, has no releases and is not published to npm; it is installed and built from source. It needs a paid or premium Planfix account with REST API access. Leads, contacts and reports are not implemented, only tasks and their related entities.
How to disable. Stop the server process and remove it from your MCP client configuration.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| PLANFIX_BASE_URL required | The Planfix account URL, for example https://company.planfix.ru. |
| PLANFIX_TOKEN required, secret | The Planfix REST API token. |
Security check
- Creates and changes tasks, comments and files in the live Planfix account
- The REST API token grants access to all account data within its permissions
README in short
The Russian README briefly lists the requirements: Node.js 18.20+, a paid Planfix account with REST API access, and a token from the account management section. It then gives a table of ten task tools with a short description of each, plus standard install, run and build commands.
FAQ
Do I need a paid Planfix account?
Yes, the README states REST API access requires a paid or premium plan.
Are leads supported?
No, only tasks and their filters, templates, comments, files and processes.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail