Planfix MCP logo

Planfix MCP

Connects AI agents to Planfix for managing tasks, contacts, projects, comments, users, custom fields, and file metadata.

Install Planfix MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "planfix-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@theyahia/planfix-mcp"
      ],
      "env": {
        "PLANFIX_API_KEY": "YOUR_VALUE_HERE",
        "PLANFIX_ACCOUNT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 20 tools correctly (15d ago).

Overview

The planfix-mcp MCP server connects AI agents to a Planfix account through the REST API. It provides 20 tools for tasks, contacts, projects, comments, employees, directories, custom fields, date tags, and files, plus two guided skills. Run it over stdio with supported desktop and coding clients or expose it through a local Streamable HTTP endpoint. Reach for it when agents need to read or update Planfix work data without using the web interface.

Use cases

  • Create tasks and assign them to Planfix employees
  • Review today’s and overdue tasks
  • Manage Planfix contacts and companies
  • Inspect projects and task comments
  • Upload files from direct URLs

Key features

  • 20 Planfix API tools
  • Task and contact CRUD operations
  • Project and comment access
  • Employee lookup and assignment support
  • Custom fields and directory access
  • Stdio and Streamable HTTP modes

Tools20

What Planfix MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.4k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

6/6 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @theyahia/planfix-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads198Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed20Callable tools this server registers over MCP.
Directory activity4 viewsConfig copies, upvotes, and views on AllMCPs.

How Planfix MCP works

What planfix-mcp MCP server does

The planfix-mcp MCP server exposes Planfix work-management and CRM data to MCP clients. Its 20 tools cover task and contact records, projects, comments, employees, directories, custom fields, date tags, and file metadata. Agents can retrieve individual records or lists, create and update tasks and contacts, add task comments, and upload a file from a direct URL.

The package also includes two skills. skill-my-tasks finds tasks due today or already overdue, while skill-create-task guides task creation by selecting a project. These skills support common prompts such as checking personal work items or creating a task in a specified project.

How it works

Requests are sent to the Planfix REST API at https://{PLANFIX_ACCOUNT}.{PLANFIX_HOST}/rest/. The server authenticates with a bearer token derived from the configured API key. PLANFIX_ACCOUNT identifies the account subdomain because Planfix does not provide one shared REST host for all accounts.

Task assignment can use list_users to find an employee ID by name before calling create_task. Status handling uses Planfix’s fixed system status values, including DRAFT, ACTIVE, ACCEPTED, COMPLETED, DELAYED, REJECTED, DONE, and CANCELED. Custom status sets are exposed through directories and directory entries.

The server can run as a standard local process or as a Streamable HTTP service. In HTTP mode, the MCP endpoint is /mcp, and a health check is available at /health.

Setup and configuration

For the planfix-mcp MCP server, provide PLANFIX_API_KEY and PLANFIX_ACCOUNT. The API key is created in Planfix account management under API access for the REST API. Set PLANFIX_HOST only when using a regional installation; it defaults to planfix.com, with planfix.ru given as an example. PLANFIX_TOKEN is supported as a legacy alternative, but the API key variable is the current option.

A local setup runs the npm package with npx -y @theyahia/planfix-mcp. Claude Desktop, Claude Code, VS Code, Cursor, and Windsurf examples are included in the project documentation. HTTP mode starts with --http followed by a port, such as --http 8080.

Tools and capabilities

  • List, retrieve, create, and update Planfix tasks.
  • List, retrieve, create, and update contacts or companies.
  • List and retrieve projects.
  • Read and add comments on tasks.
  • List and retrieve employees for assignment workflows.
  • Read directories, directory entries, custom fields, and date tags.
  • Upload a file from a direct URL and retrieve file metadata by ID.

Limitations and notes

The priority value accepted by create_task is passed through as a string; the implementation does not verify its allowed values against the live Planfix API. File uploads from a local disk using multipart requests are not implemented. Time-tracking and action endpoints are also outside the implemented API surface. File handling is limited to upload_file_from_url and metadata retrieval.

The planfix-mcp MCP server does not provide a separate task-status-list endpoint because Planfix does not expose the documented /taskstatus/list route. Use the fixed system statuses or inspect custom status directories instead.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Planfix MCP

planfix-mcp is an MCP server that connects AI agents to the Planfix REST API. Its main tools manage tasks, contacts, projects, comments, employees, directories, custom fields, date tags, and file metadata. It also includes guided skills for reviewing today’s or overdue tasks and creating a task within a selected project.

Install it by running `npx -y @theyahia/planfix-mcp` from an MCP client configuration. Set `PLANFIX_API_KEY` and `PLANFIX_ACCOUNT` in the client environment. The documentation provides configurations for Claude Desktop, Claude Code, VS Code, Cursor, and Windsurf.

It requires `PLANFIX_API_KEY` and `PLANFIX_ACCOUNT`. The API key authenticates requests, while the account value is the Planfix subdomain, such as `mycompany` from `mycompany.planfix.com`. `PLANFIX_HOST` is optional for regional installations.

Yes, planfix-mcp works with Cursor through a standard MCP server configuration. Add the package as an npx command and provide `PLANFIX_API_KEY` and `PLANFIX_ACCOUNT` in the server environment.

Yes, it can upload a file from a direct URL with `upload_file_from_url` and retrieve file metadata with `get_file`. Uploading a local file from disk through a multipart request is not implemented.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewPlanfix MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/planfix-mcp?style=directory)](https://allmcps.com/mcp/planfix-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/planfix-mcp"><img src="https://allmcps.com/api/badge/planfix-mcp?style=directory" alt="Planfix MCP on AllMCPs" /></a>