staleless
DocsStart free

Public npm package + MCP

Find stale docs before your users do.

Audit a repository in one command, run the same publishing rules in CI, and connect agents through a scoped MCP interface.

Try the package

Start with your repository.

Audit reads local code and Markdown, then names missing coverage, stale pages, API mismatches, and undocumented settings. Nothing leaves the machine.

View on npm
Public npm packagestaleless 0.1.0
npx staleless audit .
sample repositoryReady
Documentation read from docs — 18 file(s), selected automatically.
Code read from sample-repository.

Documentation Health: 78/100

   4 undocumented capabilities
   1 stale page
   0 API mismatches
   2 undocumented environment variables

Next: staleless document --dry
1 error(s), 1 warning(s) across 12 pages:

  pages/authentication.md
    ERROR [dead-link] "/tokens" does not exist
  pages/webhooks.md
    WARN  [review-overdue] review was due 9 days ago

1 problem(s) would make the published site wrong.
Read 84 files in sample-repository against 12 documentation pages.

  src/teams.ts
    api/teams.md
      GET /teams — api/teams.md:42
    guides/team-management.md
      TEAMS_PAGE_SIZE — guides/team-management.md:18

2 page(s) describe something this file changed.
Coverage, not correctness: review both pages before merging.

This runs representative output against a sample project. Run the copied command in your repository for a real result.

No account, token, or upload required

Agent access

Give tools a narrow door.

MCP is the agent interface. API tokens are the credential. The scopes say what the tool may do before it ever makes a request.

01

CLI in CI

Run lint and audit where code changes, including forked pull requests that cannot safely receive secrets.

02

Live workspace checks

Use STALELESS_TOKEN for checks that need server state: publish history, review dates, and current reader signals.

03

MCP for agents

Let compatible tools search, read, stage edits, commit a draft, and open review without giving them publish access.

04

One permission model

Tokens are scoped to documentation operations and obey the same workspace and site boundary as the product.

MCP configuration

Point the client at the hosted endpoint.

Create a token in Settings, give it only the scopes it needs, and keep it in STALELESS_TOKEN. Publishing remains a human action.

{
  "mcpServers": {
    "staleless": {
      "url": "https://mcp.staleless.com/mcp",
      "headers": {
        "Authorization": "Bearer ${STALELESS_TOKEN}"
      }
    }
  }
}
  1. 01Mint

    Create a scoped token in Staleless.

  2. 02Configure

    Add the hosted MCP endpoint to your client.

  3. 03Review

    Inspect the diff before anything reaches readers.

Start with the docs you already have

Beautiful docs are easy.
Keeping them accurate is the hard part.

Start free Talk to us