> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fallow.tools/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

> Use Fallow from agents, editors, and CI systems. MCP, VS Code, GitHub Actions, and GitLab CI.

Fallow runs in three common places:

* **Agents**: structured output and MCP tools
* **Editors**: real-time feedback while coding
* **CI**: review and merge gating

<CardGroup cols={2}>
  <Card title="MCP" icon="robot" href="/integrations/mcp">
    Typed tool calling for Claude Code, Cursor, Windsurf, and other agents.
  </Card>

  <Card title="Agent Skills" icon="sparkles" href="/integrations/agent-skills">
    Reusable agent guidance and workflows.
  </Card>

  <Card title="VS Code" icon="window" href="/integrations/vscode">
    Diagnostics, Code Lens above exports, and one-click code actions.
  </Card>

  <Card title="CI" icon="shield-check" href="/integrations/ci">
    GitHub Actions, GitLab CI, and generic pipelines.
  </Card>

  <Card title="Health badges" icon="award" href="/integrations/badges">
    Shields.io-compatible SVG badges for README files.
  </Card>
</CardGroup>

## Recommended starting point

* If you are a **developer**, start with the CLI, then add VS Code.
* If you are using **agents**, start with CLI JSON output, then add MCP.
* If you are rolling out to a **team**, start with CI, then layer in runtime intelligence later.