Three ways in. One checker. Your code stays with you.

Use Lintsure inside your coding agent, from your terminal, or in CI. All three run the same rules locally and give the same result.

What runs where

Everything inside the dashed line is your machine or your own CI. Lintsure reads your repo there and sends nothing to us.

What happens when you run a check

Six agents hand work to each other. The same steps run whether you start from your agent, your terminal or CI.

Pick how you run it

All three use the same rules. Most teams start in their coding agent, then add CI once the first gaps are fixed.

01 · MCP server

Inside your coding agent

Ask in plain words. Your agent calls Lintsure's tools, reads the findings and applies fixes you approve.

Best while you build

02 · CLI

In your terminal

One command scans the repo and writes a report. Good for a first look or a local pre-commit check.

Best for a quick check

03 · CI

On every pull request

The GitHub Action warns or fails when a change opens a new gap, so problems never reach main.

Best for teams

Set it up in a minute

Terminal

claude mcp add lintsure -- npx -y @lintsure/mcp

Then ask: "check this repo for compliance"

.cursor/mcp.json

{
  "mcpServers": {
    "lintsure": { "command": "npx", "args": ["-y", "@lintsure/mcp"] }
  }
}

Then ask: "check this repo for compliance"

~/.codex/config.toml

[mcp_servers.lintsure]
command = "npx"
args = ["-y", "@lintsure/mcp"]

Then ask: "check this repo for compliance"

~/.config/devin/mcp_config.json

{
  "mcpServers": {
    "lintsure": { "command": "npx", "args": ["-y", "@lintsure/mcp"] }
  }
}

Then ask: "check this repo for compliance"

.github/workflows/lintsure.yml

name: lintsure
on: [pull_request]
jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: lintsure/action@v1

Then ask: "check this repo for compliance"

Any repo

npx lintsure scan

Then ask: "check this repo for compliance"

The docs always match the latest release.