Changelog

You can now index documentation websites directly — no GitHub repo required. fetch_doc falls back to live scraping when a URL isn't indexed yet. And free workspaces can now create up to 3 custom libraries instead of 1.

Website Indexing

Point Docfork at any documentation site and it will crawl and index the pages for search. Go to Libraries in your dashboard, create a new library, and pick Website as the source type. Paste the root URL and Docfork queues a crawl job — the same Jobs page that tracks GitHub indexing shows progress, lets you filter by status, and lets you retry failed runs.

Once indexed, your website library is searchable in Cabinets like any GitHub-sourced library.

Website libraries count toward the same 3-library quota as private GitHub repos.

Live Fetch for fetch_doc

When fetch_doc is called with a URL that isn't yet indexed, it now automatically fetches the page live and returns the content in the same shape as an indexed result. The response includes a source field — "indexed" or "live" — so your agent can tell whether content came from Docfork's index or a fresh scrape. Live fetches are rate-limited to 30 requests per minute per workspace.

More Custom Libraries on the Free Tier

Free workspaces now get 3 custom libraries (up from 1). The quota is unified across private GitHub repos, org-scoped public repos, and website libraries — use them however fits your workflow.

Private repository indexing is now available in beta. Your AI agent can search your own private docs the same way it searches public libraries.

Private Repository Indexing

Connect GitHub from Integrations in your dashboard. Install the GitHub App (recommended) or a Personal Access Token. Pick a repo from the repo picker when creating a library — Docfork queues an index job. The Jobs page lets you monitor progress, filter by status, and retry failed runs. Once complete, the library is available across your workspace like any public one.

1 private library per workspace is included free during beta — and stays free permanently at that limit.

Library Management

The Libraries page gives you a unified view of everything indexed in your workspace — both private and public libraries. Add from GitHub, browse the public catalog, or manage existing ones from one place.

The Library Access Scope setting in Workspace Settings controls which libraries workspace API keys can search:

• Workspace Only restricts to libraries you've added (recommended for teams)
• Public Index opens access to Docfork's full public libraries catalog

Fine-grained control per API key is coming soon.

We've rebuilt our MCP tool prompts from the ground up so LLMs can understand them better. Tools are now query_docs and fetch_url. Let us know if you see improved token usage or more accurate results from Docfork MCP!

Search Descriptions

query_docs now returns semantic descriptions with each result so your agent can pick the right doc before fetching.

Smart Reads

fetch_url is now more flexible — your agent can pass a broader path instead of an exact chunk URL to discover related docs. This returns a table of contents with previews, so your agent can explore before committing to a full read.

OAuth 2.0 support is now generally available for Docfork MCP! Authenticate with your organization's identity provider and scope MCP access per user or team. Continue using API keys for fine-grained access to your Cabinets.

To get started with OAuth, update your client configuration to use the new /mcp/oauth endpoint:

{
  "mcpServers": {
    "docfork": {
      "type": "http",
-     "url": "https://mcp.docfork.com/mcp"
+     "url": "https://mcp.docfork.com/mcp/oauth"
    }
  }
}

You'll then be prompted to authenticate with docfork.com to get your OAuth token.

Ready to configure OAuth for your org? See the full setup guide.

Docfork now has a user dashboard for managing API keys, tracking usage, and creating Cabinets — project-scoped documentation indexes.

Read more in our full announcement.

User Dashboard

Sign up at app.docfork.com to access your personal dashboard.

User Dashboard

API Keys

Unlock higher rate limits and usage tracking with authenticated requests.

• 1,000 requests/month on free tier (2x industry standard)
• 5 team seats included
• Pro & Enterprise coming soon

Cabinets

Scope documentation searches to your specific tech stack. Create a cabinet with Next.js, Supabase, and Tailwind — your AI only searches those libraries.

No more irrelevant results from frameworks you don't use.

Cabinets

Get Started

Sign up: Create your free account for API keys and cabinets

Install: Add Docfork MCP in 60 seconds

Help us reach 1,000 stars ⭐ Star Docfork on GitHub

Stability improvements and fixes for common issues when running Docfork with MCP clients.

Docfork now supports HTTP transport alongside stdio, so your MCP client can connect remotely or locally. Request timeouts and config endpoints improve reliability and compatibility across clients.

HTTP Transport

Run Docfork over HTTP for remote connections or when your client prefers HTTP over stdio. Config and server discovery work the same either way.

Client Compatibility