MCP Server
MCP Server
MCP Server
MCP Server
Beta
Beta
Beta
MCP is an open protocol that empowers applications to integrate context into large language models (LLMs) and build powerful, data-driven workflows. By connecting LLMs to external tools and data sources, MCP enables more accurate outputs, deeper insights and more dynamic interactions.
This MCP server connects directly to the Planhat API, offering three core tools to explore, inspect, and operate on Planhat data models in real time. Authentication is only supported through bearer token, OAuth flows are not supported, and clients must provide a valid bearer token in the Authorization
header to establish a connection.
MCP is an open protocol that empowers applications to integrate context into large language models (LLMs) and build powerful, data-driven workflows. By connecting LLMs to external tools and data sources, MCP enables more accurate outputs, deeper insights and more dynamic interactions.
This MCP server connects directly to the Planhat API, offering three core tools to explore, inspect, and operate on Planhat data models in real time. Authentication is only supported through bearer token, OAuth flows are not supported, and clients must provide a valid bearer token in the Authorization
header to establish a connection.
MCP is an open protocol that empowers applications to integrate context into large language models (LLMs) and build powerful, data-driven workflows. By connecting LLMs to external tools and data sources, MCP enables more accurate outputs, deeper insights and more dynamic interactions.
This MCP server connects directly to the Planhat API, offering three core tools to explore, inspect, and operate on Planhat data models in real time. Authentication is only supported through bearer token, OAuth flows are not supported, and clients must provide a valid bearer token in the Authorization
header to establish a connection.
Discover models and operations
Discover available Planhat data models and their supported operations for API exploration and dynamic tool configuraiton. The output is a JSON arary of model routes with supported operations.
Get model parameter schema
Retrieve detailed parameter schemas for specific model-operation combinations, for schema validation, form generation and parameter discovery. Output is JSON schema with parameter definitions, types and requirementst. Use following as input:
MODEL_ROUTE
: Target data model (E.g. Companies)OPERATION
: Desired operation ("create"/"update"/"view"/"list")
Perform operations
Execute CRUD (Create/Read/Update/Delete) operations on Planhat data, for all types of data manipulation. Output is API response, use the following as input:
MODEL_ROUTE
: Target data modelOPERATION
: Operation typePARAMETERS
: JSON string containing operation data
Discover models and operations
Discover available Planhat data models and their supported operations for API exploration and dynamic tool configuraiton. The output is a JSON arary of model routes with supported operations.
Get model parameter schema
Retrieve detailed parameter schemas for specific model-operation combinations, for schema validation, form generation and parameter discovery. Output is JSON schema with parameter definitions, types and requirementst. Use following as input:
MODEL_ROUTE
: Target data model (E.g. Companies)OPERATION
: Desired operation ("create"/"update"/"view"/"list")
Perform operations
Execute CRUD (Create/Read/Update/Delete) operations on Planhat data, for all types of data manipulation. Output is API response, use the following as input:
MODEL_ROUTE
: Target data modelOPERATION
: Operation typePARAMETERS
: JSON string containing operation data
Discover models and operations
Discover available Planhat data models and their supported operations for API exploration and dynamic tool configuraiton. The output is a JSON arary of model routes with supported operations.
Get model parameter schema
Retrieve detailed parameter schemas for specific model-operation combinations, for schema validation, form generation and parameter discovery. Output is JSON schema with parameter definitions, types and requirementst. Use following as input:
MODEL_ROUTE
: Target data model (E.g. Companies)OPERATION
: Desired operation ("create"/"update"/"view"/"list")
Perform operations
Execute CRUD (Create/Read/Update/Delete) operations on Planhat data, for all types of data manipulation. Output is API response, use the following as input:
MODEL_ROUTE
: Target data modelOPERATION
: Operation typePARAMETERS
: JSON string containing operation data
401 Unauthorized
Caused by missing or invalid access token. Check the Authorization: Bearer <token>/<token>
and ensure token is active and valid.
403 Forbidden
Caused by token lacking permissions. Solve by updating app permissions in App Center.
404 Not Found
Caused by invalid MODEL_ROUTE
or OPERATION
. Fix by confirming supported models/operations using get_model_actions
.
400 Bad Request
Caused by missing or invalid parameters. Ensure correct types and required fields are correct by checking get_model_action_parameters
.
429 Too Many Requests
Rate limit hit. Retry with delay, use Retry-After
header if present
500 Internal Server Error
Unexpected server-side issue. Retry the request, report to Planhat Team with request details if persistent.
401 Unauthorized
Caused by missing or invalid access token. Check the Authorization: Bearer <token>/<token>
and ensure token is active and valid.
403 Forbidden
Caused by token lacking permissions. Solve by updating app permissions in App Center.
404 Not Found
Caused by invalid MODEL_ROUTE
or OPERATION
. Fix by confirming supported models/operations using get_model_actions
.
400 Bad Request
Caused by missing or invalid parameters. Ensure correct types and required fields are correct by checking get_model_action_parameters
.
429 Too Many Requests
Rate limit hit. Retry with delay, use Retry-After
header if present
500 Internal Server Error
Unexpected server-side issue. Retry the request, report to Planhat Team with request details if persistent.
401 Unauthorized
Caused by missing or invalid access token. Check the Authorization: Bearer <token>/<token>
and ensure token is active and valid.
403 Forbidden
Caused by token lacking permissions. Solve by updating app permissions in App Center.
404 Not Found
Caused by invalid MODEL_ROUTE
or OPERATION
. Fix by confirming supported models/operations using get_model_actions
.
400 Bad Request
Caused by missing or invalid parameters. Ensure correct types and required fields are correct by checking get_model_action_parameters
.
429 Too Many Requests
Rate limit hit. Retry with delay, use Retry-After
header if present
500 Internal Server Error
Unexpected server-side issue. Retry the request, report to Planhat Team with request details if persistent.
Get your Planhat API token
Navigate to App Center in Plahat
Create a new private app
Assign the necessary permissions
Generate and copy your access token
Locate and Edit the Configuration File (MacOS)
Open Finder
Press
Cmd + Shift + G
Type
~/Library/Application Support/Claude/
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Locate and Edit the Configuration File (Windows)
Open File Explorer
In address bar, type
%APPDATA%\Claude\
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Add Planhat MCP Configuration and Replace Token
Add the JSON for empty or existing configuration.
Find and replace
token
with the Planhat API tokenSave file
Restart Claude Desktop and Refresh MCP Configuration
Restart Claude Desktop
Press "Reload MCP Configuration". If it's not visible in developer tab, go to "Help" / "Troubleshooting" / "Enable developer settings"
Verify Setup
Verify hammer/connection icon in bottom right corner of chat input box
Press to see available MCP servers
Verify Planhat is listed
Alternatively, go to "Settings" / "Developer" tab to see if the server is running
Troubleshooting
Make sure NPX is downloaded
If MCP icon doesn't show, verify syntax in
claude_desktop_config.json
Verify the API token provided by private app in Planhat
Restart Claude Desktop
This setup is only for Claude Desktop, not the Web App. If configuration is to demo environment, update URL in configuration file to https://api.planhatdemo.com/v1/mcp
Example Request
Get your Planhat API token
Navigate to App Center in Plahat
Create a new private app
Assign the necessary permissions
Generate and copy your access token
Locate and Edit the Configuration File (MacOS)
Open Finder
Press
Cmd + Shift + G
Type
~/Library/Application Support/Claude/
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Locate and Edit the Configuration File (Windows)
Open File Explorer
In address bar, type
%APPDATA%\Claude\
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Add Planhat MCP Configuration and Replace Token
Add the JSON for empty or existing configuration.
Find and replace
token
with the Planhat API tokenSave file
Restart Claude Desktop and Refresh MCP Configuration
Restart Claude Desktop
Press "Reload MCP Configuration". If it's not visible in developer tab, go to "Help" / "Troubleshooting" / "Enable developer settings"
Verify Setup
Verify hammer/connection icon in bottom right corner of chat input box
Press to see available MCP servers
Verify Planhat is listed
Alternatively, go to "Settings" / "Developer" tab to see if the server is running
Troubleshooting
Make sure NPX is downloaded
If MCP icon doesn't show, verify syntax in
claude_desktop_config.json
Verify the API token provided by private app in Planhat
Restart Claude Desktop
This setup is only for Claude Desktop, not the Web App. If configuration is to demo environment, update URL in configuration file to https://api.planhatdemo.com/v1/mcp
Example Request
Get your Planhat API token
Navigate to App Center in Plahat
Create a new private app
Assign the necessary permissions
Generate and copy your access token
Locate and Edit the Configuration File (MacOS)
Open Finder
Press
Cmd + Shift + G
Type
~/Library/Application Support/Claude/
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Locate and Edit the Configuration File (Windows)
Open File Explorer
In address bar, type
%APPDATA%\Claude\
Locate
claude_desktop_config.json
.If it doesn't exist, create a new file with this name. Open with Text Editor
Add Planhat MCP Configuration and Replace Token
Add the JSON for empty or existing configuration.
Find and replace
token
with the Planhat API tokenSave file
Restart Claude Desktop and Refresh MCP Configuration
Restart Claude Desktop
Press "Reload MCP Configuration". If it's not visible in developer tab, go to "Help" / "Troubleshooting" / "Enable developer settings"
Verify Setup
Verify hammer/connection icon in bottom right corner of chat input box
Press to see available MCP servers
Verify Planhat is listed
Alternatively, go to "Settings" / "Developer" tab to see if the server is running
Troubleshooting
Make sure NPX is downloaded
If MCP icon doesn't show, verify syntax in
claude_desktop_config.json
Verify the API token provided by private app in Planhat
Restart Claude Desktop
This setup is only for Claude Desktop, not the Web App. If configuration is to demo environment, update URL in configuration file to https://api.planhatdemo.com/v1/mcp
Example Request