Server facts
planfix-mcp-server
Project
- Author
- popstas
- Repository
- github.com/popstas/planfix-mcp-server
- License
- Not specified
- Category
- Productivity
Tech
- Runtime / language
- node
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 11
- Last commit
- Data as of
Tags
- Api Integration
- mcp server
- planfix
Overview
Lead intake and follow-up are central to planfix-mcp-server: its tools can create or update a contact, task, and comment together for a lead, or handle contact and lead-task changes separately. Contact searches accept names, telephone numbers, email addresses, and Telegram details, while company lookup uses names. Task workflows include creating lead tasks, creating sales tasks from textual information or numeric identifiers, finding tasks through titles or client identifiers, adding comments, and retrieving a parent task’s children. These operations connect MCP clients to Planfix’s CRM and task management data.
Reporting tools list report names and identifiers, inspect a report’s fields, and execute a selected report to retrieve its data. Other lookups cover managers, projects, directories, and directory entries. The integration uses the Planfix REST API v2.0, runs on Node, and communicates over stdio. Configuration supplies the Planfix account, a Bearer token, and custom field identifiers for email, phone, Telegram, client, manager, and agency data.
planfix-mcp-server setup notes
- planfix-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- planfix-mcp-server has no recorded license; confirm reuse terms in its repository.