Docs

Scry documentation

How to connect over MCP, write read-only SQL against the archive, and use vectors — plus the schema, freshness, and provenance reference.

Start here

  • ConnectionScry is an MCP server at https://mcp.scry.io. Add the URL to Claude Code, Codex, ChatGPT, Claude.ai, or Cursor and approve the sign-in; per-client steps.
  • First queryThe agent calls scry_context once, scry_schema before SQL, then scry_query with a LIMIT. Rows come back with their sources.
  • HTTP APIWithout an MCP client, call GET /v1/scry/context, GET /v1/scry/schema, then POST /v1/scry/query with Content-Type: text/plain and a bearer key.

Reference

Connect Scry to ChatGPT, Claude, Codex, and other agents Add Scry as an MCP server in ChatGPT, Claude.ai, Claude Desktop and Cowork, Claude Code, Codex, Cursor, or any MCP client, then ask it structured questions over the corpus.HTTP API Use the Scry HTTP API for context, schema discovery, bounded read-only SQL, reranking, and web search.Search operators Use exact phrases, exclusions, source filters, author filters, dates, engagement floors, and language filters in Scry search.Rerank Order documents you already hold with the authenticated Scry rerank endpoint.Web search Search configured open-web providers through one authenticated Scry endpoint.Pricing and limits Understand Scry credits, congestion pricing, query metering, and the limits that keep requests bounded.Errors Handle Scry HTTP error envelopes, status codes, retry guidance, and long-query failures.Vector search and compositional embeddings Use Scry vector helpers and current academic-paper chunk embeddings together with source-native SQL filters.Schema, provenance, and freshness Inspect Scry schema, source-native tables, provenance fields, freshness state, and query-visible corpus surfaces before running broad research queries.Agent setup for Scry Connect Claude Code, Codex, or another agent to Scry over MCP, or give it an API key for the HTTP API, and let it compose bounded SQL over public corpus sources.