Developer Tools

Ship agent-ready docs

The same Glintbase scanner core, three ways to run it. Install the MCP server for in-editor audits, the CLI for CI gates, or the agent skill to teach your coding agent the whole workflow.

In-editor, interactive

MCP Server

Zero-config scanner tools your coding agent drives directly. No API keys, no .env — the agent reasons over the results.

.mcp.jsonjson
{
  "mcpServers": {
    "glintbase": {
      "command": "npx",
      "args": ["-y", "@glintbase/mcp"]
    }
  }
}
Open the MCP gateway
CI gates & scripts

CLI

Beautiful terminal output, JSON/Markdown reports, and exit codes for CI. Bring your own model (cloud or local).

Install & scanbash
npm install -g @glintbase/cli
glintbase scan https://docs.example.com
CI gatebash
npx @glintbase/cli scan https://docs.example.com --fail-under 70 --quiet
View on npm
Agent playbook

Agent Skill

Teach any coding agent when and how to use Glintbase — the golden tool sequence, score interpretation, and MCP-vs-CLI guidance.

Install the skillbash
# Claude Code
cp -r skills/glintbase-agent-readiness ~/.claude/skills/

# Qoder / .agents
cp -r skills/glintbase-agent-readiness .agents/skills/
Browse the skill

Which should I use?

WebCLIMCP
Best forHosted one-click, sharingLocal runs + CI gatesDriving from a coding agent
SetupNone (hosted)npm i -g, optional wizardZero-config, no keys
Journey engineDeterministic; LLM harness on deepDeterministic; --agent opts inAlways deterministic (agent reasons)
LLM providerHosted (Google)Yours (cloud or local)None — the agent's own
ExtractionRaw + FirecrawlRaw + FirecrawlRaw + zero-dep deep_crawl
OutputInteractive UI, badgeTerminal, JSON/MD, exit codesStructured JSON per tool
Scan Your EcosystemMCP Gateway