Cursor, Claude, and generic HTTP clients·View as Markdown

Install MCP

Create an API key first, then point your client at the Streamable HTTP endpoint.

Cursor

Add to ~/.cursor/mcp.json (or project .cursor/mcp.json):

{
  "mcpServers": {
    "file-rocks": {
      "url": "https://www.file.rocks/api/mcp",
      "headers": {
        "Authorization": "Bearer fr_live_..."
      }
    }
  }
}

Reload MCP servers in Cursor. Try list_workspaces or list_buckets.

Claude Desktop / Claude Code

If the client supports remote Streamable HTTP URLs, use the same URL + Authorization header.

For stdio-only clients, bridge with mcp-remote:

{
  "mcpServers": {
    "file-rocks": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.file.rocks/api/mcp",
        "--header",
        "Authorization: Bearer fr_live_..."
      ]
    }
  }
}

(Exact mcp-remote header flags may vary by version — check its README.)

Generic HTTP

Any MCP client that speaks Streamable HTTP can POST to:

https://www.file.rocks/api/mcp

with Authorization: Bearer fr_live_....

Local / staging

Replace the host with your deployment origin. Auth and tools behave the same.

Next

Tools reference · Auth & scopes