SkillFoxx

Type a name, a task or a service

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

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 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

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/planfix-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 'PLANFIX_ACCOUNT=<PLANFIX_ACCOUNT value>' --env 'PLANFIX_TOKEN=<your PLANFIX_TOKEN>' --env 'PLANFIX_FIELD_ID_EMAIL=<PLANFIX_FIELD_ID_EMAIL value>' --env 'PLANFIX_FIELD_ID_PHONE=<PLANFIX_FIELD_ID_PHONE value>' planfix -- npx -y @popstas/planfix-mcp-server

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

{
  "mcpServers": {
    "planfix": {
      "command": "npx",
      "args": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": {
    "planfix": {
      "command": "npx",
      "args": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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":"planfix","type":"stdio","command":"npx","args":["-y","@popstas/planfix-mcp-server"],"env":{"PLANFIX_ACCOUNT":"<PLANFIX_ACCOUNT value>","PLANFIX_TOKEN":"<your PLANFIX_TOKEN>","PLANFIX_FIELD_ID_EMAIL":"<PLANFIX_FIELD_ID_EMAIL value>","PLANFIX_FIELD_ID_PHONE":"<PLANFIX_FIELD_ID_PHONE value>"}}'

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

{
  "servers": {
    "planfix": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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_ACCOUNT=<PLANFIX_ACCOUNT value>' --env 'PLANFIX_TOKEN=<your PLANFIX_TOKEN>' --env 'PLANFIX_FIELD_ID_EMAIL=<PLANFIX_FIELD_ID_EMAIL value>' --env 'PLANFIX_FIELD_ID_PHONE=<PLANFIX_FIELD_ID_PHONE value>' -- npx -y @popstas/planfix-mcp-server

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

[mcp_servers.planfix]
command = "npx"
args = ["-y", "@popstas/planfix-mcp-server"]
env = { PLANFIX_ACCOUNT = "<PLANFIX_ACCOUNT value>", PLANFIX_TOKEN = "<your PLANFIX_TOKEN>", PLANFIX_FIELD_ID_EMAIL = "<PLANFIX_FIELD_ID_EMAIL value>", PLANFIX_FIELD_ID_PHONE = "<PLANFIX_FIELD_ID_PHONE value>" }

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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 ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "planfix": {
      "command": "npx",
      "args": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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",
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "environment": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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": [
        "-y",
        "@popstas/planfix-mcp-server"
      ],
      "env": {
        "PLANFIX_ACCOUNT": "<PLANFIX_ACCOUNT value>",
        "PLANFIX_TOKEN": "<your PLANFIX_TOKEN>",
        "PLANFIX_FIELD_ID_EMAIL": "<PLANFIX_FIELD_ID_EMAIL value>",
        "PLANFIX_FIELD_ID_PHONE": "<PLANFIX_FIELD_ID_PHONE value>"
      }
    }
  }
}

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

Keys and settings

PLANFIX_ACCOUNTrequired
Your Planfix account name (e.g., yourcompany)
PLANFIX_TOKENsecret, required
Planfix API token with necessary permissions
PLANFIX_FIELD_ID_EMAILrequired
Custom field ID for email
PLANFIX_FIELD_ID_PHONErequired
Custom field ID for phone
PLANFIX_FIELD_ID_TELEGRAMoptional
Set any value to use the system Telegram field
PLANFIX_FIELD_ID_TELEGRAM_CUSTOMoptional
Custom field ID for Telegram when using the custom field
PLANFIX_FIELD_ID_CLIENToptional
Custom field ID for client
PLANFIX_FIELD_ID_MANAGERoptional
Custom field ID for manager
PLANFIX_FIELD_ID_AGENCYoptional
Custom field ID for agency
PLANFIX_FIELD_ID_TAGSoptional
Custom field ID for task tags
PLANFIX_FIELD_ID_LEAD_IDoptional
Custom field ID for external lead ID
PLANFIX_LEAD_TEMPLATE_IDoptional
ID of the lead task template
PLANFIX_TASK_TITLE_TEMPLATEoptional
Template for the default lead task title (e.g., {name} - client's task)

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 26, 2026, commit fba7111.

Text for your agent

Install and run the server with PLANFIX_ACCOUNT=yourorg PLANFIX_TOKEN=token npx @popstas/planfix-mcp-server, and for a .ru regional install also set PLANFIX_BASE_URL.

Other ways from the author
PLANFIX_ACCOUNT=yourcompany PLANFIX_TOKEN=token npx @popstas/planfix-mcp-server

Run command from the README; for .ru accounts also add PLANFIX_BASE_URL.

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

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.

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.

Security check

  • 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

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.

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.

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 AIPlanfix MCP server

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