Planfix MCP server on FastMCP
pf-mcp-server-local
A Node.js FastMCP server for Planfix covering tasks, projects, contacts, comments and HTTP transport
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, projects, contacts and comments in the live Planfix account
- The API token grants access to all account data within its permissions
Install
Manual install
npm install && npm run startRun from source after cloning the repository and configuring .env.
This is third-party code. Review the repository files before installing.
What it does
The server wraps the Planfix REST API in MCP tools built on the FastMCP framework: an API health check, creating and reading tasks, projects, contacts and comments, plus updating and listing them. Parameters are validated with Zod schemas and requests to Planfix go through axios. The server runs as an HTTP Stream, so it can be connected to any MCP client that supports that transport without stdio.
Who it is for. For teams running tasks and projects in Planfix who want to connect an agent over HTTP rather than only a local process.
Good fit when
- You need a Planfix MCP server with HTTP transport, not only stdio
- You need basic operations on tasks, projects, contacts and comments
- You need typed parameter validation via Zod
Not a fit when
- You need leads, reports or custom fields: they are not covered
- You need a ready npm package: it only installs from source
Example request
Create a Planfix task Check the payment and assign it to manager IvanovLimitations
The project has no releases and is not published to npm as a package, only source in the repository. It has a single author, a thin README history, and no tests. Coverage is limited to tasks, projects, contacts and comments; leads and reports are not supported.
How to disable. Stop the server process and remove it from your MCP client configuration.
MCP
- Transport
- http
- Authentication
- API key
| Environment variables | |
|---|---|
| PLANFIX_API_URL required | The Planfix account REST address. |
| PLANFIX_API_TOKEN required, secret | The Planfix API token. |
| MCP_SERVER_PORT | The HTTP server port, 3030 by default. |
Security check
- Creates and changes tasks, projects, contacts and comments in the live Planfix account
- The API token grants access to all account data within its permissions
README in short
The English README lists the features: an API check, a full set of operations on tasks, projects, comments, users and contacts, HTTP Stream Transport, type safety via Zod, and the FastMCP framework. It lists the available tools with a short description of each, including a ping check for API availability.
FAQ
What transport does the server use?
HTTP Stream Transport, with the port set via MCP_SERVER_PORT.
Do I need a Planfix token?
Yes, PLANFIX_API_TOKEN with access to the target account, set in .env.
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