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.
Make sure you have the following environment variables set in your .env file:
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://.planfix.com/webchat/api.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"}'Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| planfix_create_sell_task | |
| planfix_create_sell_task_ids | |
| leadToTask | Convert a lead to a task by creating/updating contact and task |
| searchLeadTask | Search for lead tasks by contact information |
| searchPlanfixContact | Search contacts by name, phone, email, or Telegram. |
| createPlanfixContact | Create a new contact in Planfix. Accepts an optional |
| updatePlanfixContact | Update existing contact information. Accepts an optional |
| searchPlanfixCompany | Search for companies by name |
| searchPlanfixTask | Search for tasks by title, client ID and optional templateId |
| createSellTask | Resolve contact/agency IDs and create a sell task |
| createSellTaskIds | Create a sell task when IDs are already known |
| createLeadTask | Create a new lead task. When chatApi.useChatApi |
| addToLeadTask | Create or update a lead task and update contact details. |
| createTask | Create a task using text fields |
| createComment | Add a comment to a task |
| getChildTasks | Retrieve child tasks of a parent task. Use recursive to |
| updateLeadTask | Update an existing lead task (only empty fields are updated unless forceUpdate is true) |
| planfix_search_directory | Search directories by name |
| planfix_search_directory_entry | Search directory entry by directory name and entry name |
| searchManager | Find a manager by email |
| listReports | List all available reports |
| runReport | Generate and retrieve a specific report |
{
"mcpServers": {
"planfix": {
"command": "npx",
"args": [
"-y",
"@popstas/planfix-mcp-server"
],
"env": {
"PLANFIX_ACCOUNT": "yourcompany",
"PLANFIX_TOKEN": "YOUR_PLANFIX_TOKEN",
"PLANFIX_FIELD_ID_EMAIL": "123",
"PLANFIX_FIELD_ID_PHONE": "124",
"PLANFIX_FIELD_ID_TELEGRAM": "1",
"PLANFIX_FIELD_ID_TELEGRAM_CUSTOM": "125",
"PLANFIX_FIELD_ID_CLIENT": "126",
"PLANFIX_FIELD_ID_MANAGER": "127",
"PLANFIX_FIELD_ID_AGENCY": "128",
"PLANFIX_FIELD_ID_TAGS": "129",
"PLANFIX_FIELD_ID_LEAD_ID": "130",
"PLANFIX_LEAD_TEMPLATE_ID": "42",
"PLANFIX_TASK_TITLE_TEMPLATE": "{name} - работа с клиентом"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Make sure you have the following environment variables set in your .env file:
| Variable | Description | Required |
|---|---|---|
| PLANFIX_ACCOUNT | Declared in the maintainer’s client configuration. | Optional |
| PLANFIX_TOKEN | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_EMAIL | Declared in the maintainer’s client configuration. | Optional |
| PLANFIX_FIELD_ID_PHONE | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_TELEGRAM | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_TELEGRAM_CUSTOM | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_CLIENT | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_MANAGER | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_AGENCY | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_TAGS | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_FIELD_ID_LEAD_ID | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_LEAD_TEMPLATE_ID | Declared in the maintainer’s client configuration. | Check documentation |
| PLANFIX_TASK_TITLE_TEMPLATE | Declared in the maintainer’s client configuration. | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
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.