MCP, API and webhooks

Connect Hillchart to the tools where work already happens

A hill chart is more useful when it can participate in the rest of your workflow. Hillchart provides authenticated interfaces for reading and updating project information, plus outgoing webhooks for selected project events.

Give AI tools structured project context

Connect an MCP-compatible client, including Cursor, to Hillchart with a personal API token. The MCP server exposes project operations as tools, so an assistant can work with structured Hillchart data instead of relying on pasted status notes.

Review the tool call and its target project just as you would review any other automated change.

Build against the API

The API uses the same token-based access for programmatic workflows. It can retrieve project data and supports snapshot operations, making it possible to connect internal scripts or services without automating the browser.

  • Create a token in Hillchart settings
  • Store tokens as secrets, never in source control
  • Limit each integration to the operations it needs

React to project events with webhooks

Configure a webhook endpoint to receive supported Hillchart events, such as scope movements or snapshots. Verify deliveries in your service and make handlers idempotent so retries remain safe.

MCP is suited to interactive AI workflows, the API to direct application calls, and webhooks to event-driven automation.