Planfix MCP server generated from the OpenAPI spec
PlanfixMCP
A FastMCP Planfix server whose tools are generated from the OpenAPI spec, with a read-only mode and data export
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
- Without PLANFIX_READ_ONLY the server can create and change tasks, contacts and projects
- The API token grants access to all account data within its permissions
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/planfixmcpDetects 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_API_TOKEN=<your PLANFIX_API_TOKEN>' planfix -- uvx run planfix-mcp --env-file .envOr add to the file .mcp.json, in the project
{
"mcpServers": {
"planfix": {
"command": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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":"uvx","args":["run","planfix-mcp","--env-file",".env"],"env":{"PLANFIX_BASE_URL":"<PLANFIX_BASE_URL value>","PLANFIX_API_TOKEN":"<your PLANFIX_API_TOKEN>"}}'Or add to the file .vscode/mcp.json, in the project
{
"servers": {
"planfix": {
"type": "stdio",
"command": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the servers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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_API_TOKEN=<your PLANFIX_API_TOKEN>' -- uvx run planfix-mcp --env-file .envOr add to the file ~/.codex/config.toml, for all projects
[mcp_servers.planfix]
command = "uvx"
args = ["run", "planfix-mcp", "--env-file", ".env"]
env = { PLANFIX_BASE_URL = "<PLANFIX_BASE_URL value>", PLANFIX_API_TOKEN = "<your PLANFIX_API_TOKEN>" }If the file already exists, append the block to the end.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_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
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": [
"uvx",
"run",
"planfix-mcp",
"--env-file",
".env"
],
"environment": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcp key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the context_servers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
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": "uvx",
"args": [
"run",
"planfix-mcp",
"--env-file",
".env"
],
"env": {
"PLANFIX_BASE_URL": "<PLANFIX_BASE_URL value>",
"PLANFIX_API_TOKEN": "<your PLANFIX_API_TOKEN>"
}
}
}
}If the file already exists, add the server inside the mcpServers key.
Keys and settings
PLANFIX_BASE_URLrequired- Базовый URL REST API ПланФикс
PLANFIX_API_TOKENsecret, required- Bearer-токен авторизации
PLANFIX_EXCLUDE_TECHNICAL_COMMENTSoptional- Если true, скрывает технические события в ленте комментариев
PLANFIX_READ_ONLYoptional- Если true, включает режим только для чтения
PLANFIX_TAGSoptional- Список тегов OpenAPI для фильтрации инструментов
PLANFIX_EXPORT_DIRoptional- Базовый каталог для выгрузки задач в файлы
PLANFIX_EXPORT_ACCOUNToptional- Имя аккаунта для имён файлов и frontmatter
PLANFIX_EXPORT_COMMENTS_PER_FILEoptional- Сколько комментариев в одном файле Markdown
Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.
Install uv, clone the repository, run uv sync, set PLANFIX_BASE_URL and PLANFIX_API_TOKEN in .env per the README, and start the server with the planfix-mcp command.
Other ways from the author
git clone <url> && cd PlanfixMCP && uv syncThe install from the README after configuring .env with PLANFIX_BASE_URL and PLANFIX_API_TOKEN.
This is third-party code. Review the repository files before installing.
What it does
The server builds its MCP tools for Planfix tasks, contacts, projects and comments by generating them from the OpenAPI spec via FastMCP.from_openapi rather than describing them by hand. REST API access is configured with a base URL and a Bearer token, with permissions chosen inside Planfix's own REST API section. A PLANFIX_READ_ONLY mode can be turned on, the operation set can be narrowed with include or exclude variables, and comment export to files can be configured.
Who it is for. For developers who want their tool set to stay in sync with the Planfix spec and to have a safe read-only mode available.
Good fit when
- You need a Planfix MCP server whose tools are generated from the official OpenAPI spec
- You need a safe read-only mode via PLANFIX_READ_ONLY
- You need to narrow the operation set by id via include or exclude
Not a fit when
- You need ready MCP resources and prompts: this server only provides tools
- You need a published npm or PyPI package: it installs from source via uv
Example request
Find all open Planfix tasks for the project Website launch and show their statusesLimitations
The project has no releases and is not published as a package; it installs from source with uv sync. Since tools are generated from the OpenAPI spec, their set and descriptions depend on how current that spec was at generation time. A Planfix REST API token with configured scopes is required.
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 account REST API base URL, for example https://account.planfix.com/rest. |
| PLANFIX_API_TOKEN required, secret | The Planfix REST API Bearer token. |
| PLANFIX_READ_ONLY | Turns on read-only mode, disabling mutating operations. |
Security check
- Without PLANFIX_READ_ONLY the server can create and change tasks, contacts and projects
- The API token grants access to all account data within its permissions
README in short
The Russian README describes installing via uv sync, obtaining a Bearer token in Planfix's REST API section, and the recommended access scopes, emphasizing the read-only mode. It separately covers .env configuration: base URL, token, operation restrictions and comment export settings.
FAQ
How do I get a token for the server?
In Planfix: Account management, Integrations, REST API. Access scopes are chosen there too; the recommended minimum is read-only.
Can the operation set be narrowed?
Yes, with PLANFIX_INCLUDE_OPERATION_IDS and PLANFIX_EXCLUDE_OPERATION_IDS, or by turning on PLANFIX_READ_ONLY.
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