MCP server for Planfix API integration
Planfix mcp server connects Planfix to AI assistants that speak the Model Context Protocol. MCP server for Planfix API integration.
This MCP server provides integration with the Planfix API, allowing Model Context Protocol (MCP) clients to interact with Planfix CRM and task management system.
Once connected, the assistant can call these 10 tools directly:
chatApiToken — token for Planfix Chat API requestsproviderId — identifier of the chat provider configured in PlanfixuseChatApi — enable Chat API integration. When true, task creation proceeds as:baseUrl — base URL for Chat API calls. Defaults to https://.planfix.com/webchat/apiWebhook — To post lead task payloads to a webhook before creating or updating a task, add a webhook block to config.yml:Logging — Set LOG_LEVEL=debug to enable detailed cache logs. Logs are written to data/mcp.logPrerequisites — Make sure you have the following environment variables set in your .env file:planfix_create_sell_task — The planfix_create_sell_task tool exposed by this serverplanfix_create_sell_task_ids — 5. Update an object (PUT request) bash npm run planfix put task/123 --data '{"name":"Updated Task Name"}'Reporting — The Reporting tool exposed by this serverThe server is distributed via npm as @popstas/planfix-mcp-server, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 8 environment variables: PLANFIX_ACCOUNT, PLANFIX_TOKEN, PLANFIX_FIELD_ID_EMAIL, PLANFIX_FIELD_ID_PHONE, PLANFIX_FIELD_ID_TELEGRAM, PLANFIX_FIELD_ID_TELEGRAM_CUSTOM, PLANFIX_FIELD_ID_CLIENT, PLANFIX_FIELD_ID_MANAGER. Keep credentials in your client's env block or a secrets manager rather than committing them.
Make sure you have the following environment variables set in your .env file:
Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Planfix sits in that group, and the shape of its toolset — chatApiToken, providerId, useChatApi among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| chatApiToken | token for Planfix Chat API requests. |
| providerId | identifier of the chat provider configured in Planfix. |
| useChatApi | enable Chat API integration. When true, task creation proceeds as: |
| baseUrl | base URL for Chat API calls. Defaults to https://<account>.planfix.com/webchat/api. |
| Webhook | To post lead task payloads to a webhook before creating or updating a task, add a webhook block to config.yml: |
| Logging | Set LOG_LEVEL=debug to enable detailed cache logs. Logs are written to data/mcp.log. |
| Prerequisites | Make sure you have the following environment variables set in your .env file: |
| planfix_create_sell_task | The planfix_create_sell_task tool exposed by this server. |
| planfix_create_sell_task_ids | 5. **Update an object (PUT request)** bash npm run planfix put task/123 --data '{"name":"Updated Task Name"}' |
| Reporting | The Reporting tool exposed by this server. |
{
"mcpServers": {
"planfix": {
"command": "npx",
"args": ["-y", "@popstas/planfix-mcp-server"],
"env": {
"PLANFIX_ACCOUNT": "your-value",
"PLANFIX_TOKEN": "your-value",
"PLANFIX_FIELD_ID_EMAIL": "your-value",
"PLANFIX_FIELD_ID_PHONE": "your-value",
"PLANFIX_FIELD_ID_TELEGRAM": "your-value",
"PLANFIX_FIELD_ID_TELEGRAM_CUSTOM": "your-value",
"PLANFIX_FIELD_ID_CLIENT": "your-value",
"PLANFIX_FIELD_ID_MANAGER": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Make sure you have the following environment variables set in your .env file:
| Variable | Description | Required |
|---|---|---|
| PLANFIX_ACCOUNT | Configuration value read at startup. | Optional |
| PLANFIX_TOKEN | Credential the server authenticates with. | Yes |
| PLANFIX_FIELD_ID_EMAIL | Configuration value read at startup. | Optional |
| PLANFIX_FIELD_ID_PHONE | Configuration value read at startup. | Optional |
| PLANFIX_FIELD_ID_TELEGRAM | Configuration value read at startup. | Optional |
| PLANFIX_FIELD_ID_TELEGRAM_CUSTOM | Configuration value read at startup. | Optional |
| PLANFIX_FIELD_ID_CLIENT | Configuration value read at startup. | Optional |
| PLANFIX_FIELD_ID_MANAGER | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.