Planfix MCP Server
by popstas
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| baseUrl | No | Base URL for Chat API calls | |
| LOG_LEVEL | No | Set to debug for detailed cache logs | |
| providerId | No | Identifier of the chat provider configured in Planfix | |
| useChatApi | No | Enable Chat API integration (true/false) | |
| chatApiToken | No | Token for Planfix Chat API requests | |
| PLANFIX_TOKEN | Yes | Planfix API token with necessary permissions | |
| PLANFIX_CONFIG | No | Path to config.yml file | |
| PLANFIX_ACCOUNT | Yes | Your Planfix account name (e.g., yourcompany) | |
| PLANFIX_BASE_URL | No | Override the REST API base URL. Defaults to https://<PLANFIX_ACCOUNT>.planfix.com/rest/. | |
| PLANFIX_ACCOUNT_URL | No | Override the web origin used for human-facing links. Defaults to PLANFIX_BASE_URL without trailing /rest/. | |
| PLANFIX_FIELD_ID_TAGS | No | Custom field ID for task tags | |
| PLANFIX_FIELD_ID_EMAIL | No | Custom field ID for email | |
| PLANFIX_FIELD_ID_PHONE | No | Custom field ID for phone | |
| PLANFIX_FIELD_ID_AGENCY | No | Custom field ID for agency | |
| PLANFIX_FIELD_ID_CLIENT | No | Custom field ID for client | |
| PLANFIX_FIELD_ID_LEAD_ID | No | Custom field ID for external lead ID | |
| PLANFIX_FIELD_ID_MANAGER | No | Custom field ID for manager | |
| PLANFIX_LEAD_TEMPLATE_ID | No | ID of the lead task template | |
| PLANFIX_FIELD_ID_PIPELINE | No | Custom field ID for pipeline | |
| PLANFIX_FIELD_ID_TELEGRAM | No | Set any value to use the system Telegram field | |
| PLANFIX_TASK_TITLE_TEMPLATE | No | Template for the default lead task title | |
| PLANFIX_FIELD_ID_LEAD_SOURCE | No | Custom field ID for lead source | |
| PLANFIX_FIELD_ID_TELEGRAM_CUSTOM | No | Custom field ID for Telegram when using the custom field | |
| PLANFIX_FIELD_ID_LEAD_SOURCE_VALUE | No | Value ID for default lead source |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/popstas/planfix-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server