Jina Docs
Wiki

Use Wiki and Scenarios through MCP

Create one scoped workspace token for repository documentation and user-flow validation.

Create a token

  1. Open Access tokens and create a workspace MCP token.
  2. Use context:read for releases/documents and context:query for search.
  3. Use scenarios:read or scenarios:write for the Scenario library, and reviews:run or reviews:read for execution.
  4. Grant context:build only when an administrator must admit exact-SHA generation.
  5. Copy the token once, store it in an environment variable, and revoke it when no longer needed.

MCP

Jina exposes one stateless Streamable HTTP server. The tools advertised to a workspace token are the union of its Wiki and Scenario scopes. Automatically issued review credentials remain pinned to one immutable release.

  • list_wiki — list releases visible to the credential.
  • search_wiki — full-text search within one immutable release.
  • read_wiki — read one generated Markdown document.
  • build_wiki — administrator-only exact-SHA admission with context:build.
  • review — run the standard review against a pull request or commit.
  • scenarios_list, scenario_put, scenario_archive — inspect and atomically maintain saved user flows.
  • scenarios_run — run ordinary exploratory reviews using relevant, selected, or all (up to 10) Scenarios as human review context against the latest default branch, a PR, or a commit.
  • scenarios_update, work_result — refresh from a branch/PR/commit, then poll the actual created, revised, archived, or unchanged results and report links.
  • Each repository keeps at most 50 active scenarios; each run remains bounded to 10 selected flows (three for automatic PR reviews). Archive obsolete flows before adding replacements.
~/.codex/config.toml
[mcp_servers.jina]
url = "https://api.usejina.com/mcp"
bearer_token_env_var = "JINA_MCP_TOKEN"
enabled_tools = ["search_wiki", "list_wiki", "read_wiki", "build_wiki", "review", "scenarios_list", "scenario_put", "scenario_archive", "scenarios_run", "scenarios_update", "work_result"]
startup_timeout_sec = 10
tool_timeout_sec = 30

HTTP API

Wiki HTTP endpoints use a separate jina_atk_ credential. Workspace jina_mcp_ credentials are for MCP. Responses are marked Cache-Control: no-store.

Endpoints
GET  https://api.usejina.com/v1/wiki/releases
GET  https://api.usejina.com/v1/wiki/documents?release_id=<uuid>&path=<path>
GET  https://api.usejina.com/v1/wiki/search?release_id=<uuid>&q=<query>
POST https://api.usejina.com/v1/wiki/build