Product MCP server
Connect MCP-compatible clients to read-only, organization-scoped Sight project evidence.
The product MCP server exposes organization-scoped Sight evidence to compatible assistants over local stdio or stateless Streamable HTTP. It delegates authorization and rate limiting to the same public API contract used by other integrations.
Tools are intentionally read-only and cover projects, scans, scores, reports, prompts, answers, sources, source gaps, domains, URLs, actions, alerts, credits, and crawl insights. Native prompts provide repeatable evidence-first analysis instructions.
Treat MCP output as evidence access, not an authorization bypass. Keep API keys scoped and revocable, review the cited project identifiers behind material claims, and use REST or the SDK when a workflow needs an intentional state change.
Choose a transport
The same server supports local stdio and stateless Streamable HTTP. Both use a Sight API key and enforce the public REST API's organization boundary.
SIGHT_API_KEY=wrk_your_secret \
SIGHT_API_URL=https://YOUR_SIGHT_HOST \
bun run mcpPOST https://YOUR_SIGHT_HOST/mcp
Authorization: Bearer wrk_your_secret
Content-Type: application/json
Accept: application/json, text/event-stream| Capability | Examples |
|---|---|
| Project state | List projects, inspect project overview, scans, and latest scores |
| Evidence | Reports, prompts, answers, sources, source gaps, domains, URLs, and actions |
| Operations | Alerts, alert rules and preferences, credit balance and ledger, and crawl insights |
| Native prompts | Visibility summary, SEO priorities, source-gap analysis, competitor comparison, scan changes, and client readout |
Read-only by design
MCP tools do not start scans or mutate project state. Use the REST API, SDK, or CLI for authorized write operations.