Files
zeekay f9fdfcd098 State a version once
A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.
2026-08-29 18:14:03 -07:00
..
2025-06-09 13:07:29 -05:00
2025-04-30 12:36:49 -05:00
2025-06-16 12:56:48 -05:00
2025-04-30 12:36:49 -05:00
2026-08-29 18:14:03 -07:00
2025-04-30 12:36:49 -05:00
2025-04-30 12:36:49 -05:00

Cloudflare AutoRAG MCP Server 📡

This is a Model Context Protocol (MCP) server that supports remote MCP connections, with Cloudflare OAuth built-in.

It integrates tools powered by the Cloudflare AutoRAG API to allow you to access and query your account's AutoRAG instances.

🔨 Available Tools

Currently available tools:

Tool Description
list_rags Lists AutoRAGs with pagination support
search Searches documents in a specified AutoRAG using a query (URL, title, or snippet)
ai_search Performs AI-powered search on documents in a specified AutoRAG

This MCP server is still a work in progress, and we plan to add more tools in the future.

Prompt Examples

  • List all AutoRAGs in my account.
  • Search for documents in AutoRAG with ID 'rag123' using the query 'cloudflare security'.
  • Perform an AI search in AutoRAG with ID 'rag456' for 'best practices for vector stores'.

Access the remote MCP server from any MCP Client

If your MCP client has first class support for remote MCP servers, the client will provide a way to accept the server URL (https://autorag.mcp.cloudflare.com) directly within its interface (for example inCloudflare AI Playground).

If your client does not yet support remote MCP servers, you will need to set up its resepective configuration file using mcp-remote (https://www.npmjs.com/package/mcp-remote) to specify which servers your client can access.

Replace the content with the following configuration:

{
	"mcpServers": {
		"cloudflare": {
			"command": "npx",
			"args": ["mcp-remote", "https://autorag.mcp.cloudflare.com/sse"]
		}
	}
}

Once you've set up your configuration file, restart MCP client and a browser window will open showing your OAuth login page. Proceed through the authentication flow to grant the client access to your MCP server. After you grant access, the tools will become available for you to use.

Interested in contributing, and running this server locally? See CONTRIBUTING.md to get started.