> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling.md).

# Set Up Developer Tooling

Install Heeler's developer tooling — the CLI, Agent Skills, and MCP server — so checks run where developers work: locally, in CI, and inside AI agents.

Beyond the connected platform, Heeler ships tooling that runs **where developers work** — at the keyboard, in CI, and inside AI coding agents. These are optional and can be added any time after your core setup. This section covers **installing and deploying** them; how you *use* each day-to-day lives under [Prevent](/mrecEO40m5D6bt7Pq5pE/prevent.md).

## What to set up

<table data-view="cards"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>CLI</strong></td><td>Install <code>heelercli</code> as a pre-commit hook and in CI.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/cli.md">Install the CLI</a></td></tr><tr><td><strong>Agent Skills</strong></td><td>Drop Heeler-backed skills into your AI agents with dotagents.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/agent-skills.md">Install Agent Skills</a></td></tr><tr><td><strong>MCP server</strong></td><td>Connect an AI agent to Heeler's live security context over MCP.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/mcp.md">Connect the MCP Server</a></td></tr></tbody></table>

## How they fit together

<table><thead><tr><th width="170">Tool</th><th>What it's for</th><th>How you use it</th></tr></thead><tbody><tr><td><strong>CLI</strong></td><td>Scan for secrets, vulnerabilities, licenses, malicious packages, and risky agent files locally and in CI.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/prevent/cli.md">Prevent → CLI</a></td></tr><tr><td><strong>Agent Skills</strong></td><td>Run those same checks from an AI agent in natural language.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/prevent/agent-skills.md">Prevent → Agent Skills</a></td></tr><tr><td><strong>MCP server</strong></td><td>Give an agent live, read-only Heeler context as it writes code.</td><td><a href="/mrecEO40m5D6bt7Pq5pE/prevent/mcp.md">Prevent → MCP Server</a></td></tr></tbody></table>

{% hint style="info" %}
These bring Heeler's checks **left** — to the developer's machine and their AI agent — complementing the [PR guardrails](/mrecEO40m5D6bt7Pq5pE/prevent/pr-guardrails.md) that gate code at merge time.
{% endhint %}

## Related

* [Install the CLI](/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/cli.md) — the foundation the Agent Skills call.
* [Install Agent Skills](/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/agent-skills.md) — in-agent checks as code is written.
* [Connect the MCP Server](/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling/mcp.md) — expose Heeler's context to your AI tools.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/set-up-developer-tooling.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.