Planhat is automatable through its API

Planhat is automatable today through its REST API. The introduction says general requests use https://api.planhat.com and user tracking and metrics use https://analytics.planhat.com. API keys are documented for the full data API. A few open endpoints accept pushes such as metrics and user activities without authentication. The authentication page says a Private App API Access Token is sent as Authorization Bearer, or as Basic with the token and a trailing colon, base64-encoded. Permissions are set on the Private App. That page still says a token lasts forever. The help center article, dated 23 July 2026, says a new token has an expiry, default 30 days and at most 365 days, and that tokens with no expiry are deprecated. The main API soft limit is 200 calls per minute, with a hard limit of 150 requests per second. Planhat also documents a hosted MCP server at https://api.planhat.com/v1/mcp for Claude, ChatGPT, and custom apps. The recommended connection is an OAuth client from App Center. What the server can reach is the overlap of that client's permissions and the user's permissions. The published tools list, get, search, create, update, and delete records, and they create, get, and search documents. search_records returns about 20 hits and is described as not an exhaustive export. The repository github.com/da-troll/Planhat-MCP is a separate local server. Its GitHub description calls it unofficial. The README documents 60 local tools that use a Planhat API token. GitHub reported a push on 2026-10-14. Connector catalogs were not opened. Computer-use viability is unassessed. The API and the hosted MCP server each score 7. The API is the best path because the introduction describes API keys as access to the full data API, while hosted MCP search is capped and OAuth access is the overlap of two permission layers.

Best path today: api · Overall automatability: 7/10