Skip to main content
The Draftt MCP server connects your LLM or coding agent directly to Draftt’s tech debt intelligence. Draftt acts as the intelligence layer: surfacing findings, upgrade plans, ownership, and policy context. The agent acts on that intelligence, opening PRs, creating tickets, updating configurations, or walking an engineer through a remediation step by step. This is the bridge between Draftt’s governance data and the AI tools your engineering teams already use.

What It Enables

Remediation, not just reporting. Instead of surfacing a finding and waiting for a human to act, an LLM agent can read the Draftt upgrade plan for an EOL dependency, understand the required steps, and open a PR, create a ticket, or execute the fix directly, grounded in Draftt’s guidance. Grounded in your environment. The agent has access to the actual resource state, ownership, blast radius, and Draftt’s recommended remediation path. Every decision is scoped to your specific stack and your specific findings, not a generic playbook. Governed by your policies. The MCP exposes your active governance policies so the agent understands what “good” looks like for your organization and can validate its actions against your standards before applying them.

Example Interactions

  • “Show me all EOL resources owned by the platform team and open PRs for each”
  • “What does Draftt recommend for upgrading PostgreSQL 11 in the payments service? Apply it”
  • “Find all high-severity findings with no open ticket and create Jira issues for each”
  • “Using the draftt MCP get the forecast for Amazon RDS MySQL extended support fees in the following 5 months”
  • “What configuration violations exist in production, and what are the fix steps?”
  • “Walk me through the upgrade guide for the EKS cluster in the payments account”
  • “Using the draftt MCP create a detailed upgrade plan for <clusterName> from 1.33 to 1.34. Use the available data to produce cluster-specific commands, not generic options”
  • “Using the draftt MCP get compatibility data for the K8s workloads in cluster <clusterName> and how to fix incompatible workloads. Provide with commands to run in order to upgrade the relevant Helm chart releases or K8s manifests.”
  • “Using the draftt MCP get the K8s Nodes status for both clusters <clusterName> and <clusterName>. Then compare their state - how many issues on each cluster and how each cluster Nodes are managed”

Connecting the MCP Server

The Draftt MCP server is published as an npm package: @draftt-io/draftt-mcp. You will need your Draftt API key, which you can generate in Settings > User Management > API Keys. Prerequisites Quick start with npx:
Claude Desktop configuration: Add the following to your claude_desktop_config.json (on macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):
Configuration variables:

Available Tools