Planfix MCP server on FastMCP
pf-mcp-server-local
A Node.js FastMCP server for Planfix covering tasks, projects, contacts, comments and HTTP transport
- 1 ★ on the repository
- Last commit
- MIT
Extended access
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
- Works in
- Services
Manual install
npm install && npm run startRun from source after cloning the repository and configuring .env.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- 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
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 IvanovMCP
- Transport
- http
- Authentication
- API key
Environment variables
PLANFIX_API_URLrequired- The Planfix account REST address.
PLANFIX_API_TOKENrequired, secret- The Planfix API token.
MCP_SERVER_PORT- The HTTP server port, 3030 by default.
Limitations
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.
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.
Discussion
No questions or reviews yet.
Related
All Planfix toolsA FastMCP Planfix server whose tools are generated from the OpenAPI spec, with a read-only mode and data export
Compact Planfix MCP server
Planfix MCP Server
A lightweight TypeScript Planfix MCP server for tasks: cards, filtered lists, creation, updates, comments and files
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
Planfix MCP
planfix-mcp
Planfix MCP server: tasks, projects, contacts, comments and employees through the REST API
Planfix MCP server with prompts and resources
Planfix MCP Server
A Python Planfix MCP server: tasks, projects, contacts and reports, plus ready MCP resources and planning prompts
Unofficial read-only Planfix MCP server
planfix-mcp
An unofficial Planfix MCP server with 93 read operations via the web client interface: tasks, comments, webhooks, integrations
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.