Planhat MCP

What the Planhat MCP MCP server does

The Planhat MCP MCP server gives AI clients access to Planhat customer and operational data through MCP. It covers companies, contacts, opportunities, notes, conversations, users, assets, issues, tickets, tasks, licenses, and invoices. Each resource has tools for listing records, retrieving an individual record, creating records, updating records, and deleting records.

The available operations support common customer-data workflows. An agent can find companies with upcoming license renewals, inspect related customer information, list support tickets or conversations, create follow-up tasks, and change existing Planhat records. The actual records and actions available still depend on the permissions assigned to the Planhat API token.

How it works

The server runs locally and communicates with the MCP client over stdio. It calls the Planhat REST API using a standard API token, so the connection does not require a hosted connector or an intermediary service. The repository builds a dependency-free JavaScript server at dist/server.js.

Every tool includes MCP read-only and destructive-operation annotations. Clients may use those signals when deciding how to present approval prompts, but the client controls its own prompting behavior. The token's Planhat permissions remain the underlying access control.

Setup and configuration

For Claude Desktop, download the .mcpb release bundle and open it to start the extension installation flow. The installer requests a Planhat token and stores it in the system keychain. It also provides options to enable read-only mode or disable delete tools.

Manual installation requires Node.js 18 or newer. Clone the repository, run npm install, build with npm run build, and place the token in a .env file as PLANHAT_TOKEN. Register the resulting dist/server.js file in the MCP client's configuration and restart the client. The documented manual configuration includes Claude Desktop and Cursor.

The Planhat MCP MCP server also supports two optional restrictions: PLANHAT_READ_ONLY=1 removes create, update, and delete tools, while PLANHAT_DISABLE_DELETE=1 keeps other operations available but removes deletion. Treat the token like a password when using a manual .env file.

Tools and capabilities

The 60 tools are organized across these Planhat resource types:

• Companies and contacts
• Opportunities, notes, and conversations
• Users, assets, issues, and tickets
• Tasks, licenses, and invoices

For each type, the corresponding list, get, create, update, and delete operations are available unless restricted by read-only or delete settings. Read-only tokens can also limit the connector regardless of local configuration. The project includes offline tests for the tool definitions and HTTP behavior; those tests do not call the live Planhat API.

Limitations and notes

The Planhat MCP MCP server requires a valid Planhat API token, and creating one requires Planhat administrator access through the Service Accounts or Private Apps settings. An HTTP 401 result usually indicates an incorrect, expired, or rotated token. An empty result can simply mean that the selected resource has no records matching the filters.

Claude Desktop must be fully restarted after configuration changes because it reads its MCP configuration at launch. Installing both the bundle and a previous manual entry can cause every tool to appear twice. The bundled installation is specifically documented for Claude Desktop; manual configuration is the route described for other MCP clients.

The project is released under the MIT license. Downloaded bundles include a SHA-256 checksum file that can be checked on macOS or Linux with shasum.