MCP Server

@reloops/mcp-server is an MCP server for Reloops. It wraps the same public API used by developer keys, so any MCP-compatible agent can list workspaces, search and upload assets, leave comments, manage versions, and create share links, all from a prompt. The server runs locally as a subprocess of your MCP client (stdio transport). Your API key stays on your machine and is only ever sent to api.reloops.app.

@reloops/mcp-server is in beta. Tool names and behavior may still change before a stable 1.0 release.

Get a developer key

The server authenticates with a reloops_live_... developer key, the same kind used by the CLI and public API. Create one from Manage Team → AI Agents & Developer Keys. See AI Agents and Developer Keys for the full walkthrough.

Connect your client

Every client runs the same command under the hood: npx -y @reloops/mcp-server, with RELOOPS_API_KEY set to your developer key. Pick your client below for the exact file and config.

Open Settings → Developer → Edit Config in Claude Desktop or Claude Code. This opens the config file below. Paste the block in, then restart the app.

claude_desktop_config.json

{
  "mcpServers": {
    "reloops": {
      "command": "npx",
      "args": ["-y", "@reloops/mcp-server"],
      "env": {
        "RELOOPS_API_KEY": "your_key_here"
      }
    }
  }
}

Run this in your terminal. It registers the server for you, no file editing needed.

claude mcp add reloops -e RELOOPS_API_KEY=your_key_here -- npx -y @reloops/mcp-server

Add this file to your project, or create it at ~/.cursor/mcp.json to enable it in every project.

.cursor/mcp.json

{
  "mcpServers": {
    "reloops": {
      "command": "npx",
      "args": ["-y", "@reloops/mcp-server"],
      "env": {
        "RELOOPS_API_KEY": "your_key_here"
      }
    }
  }
}

Add this file to your project, or run MCP: Add Server from the Command Palette instead of editing it by hand.

.vscode/mcp.json

{
  "servers": {
    "reloops": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@reloops/mcp-server"],
      "env": {
        "RELOOPS_API_KEY": "your_key_here"
      }
    }
  }
}

VS Code uses servers at the top level, not mcpServers, and needs an explicit "type": "stdio" field.

Add this to your Codex config, or run the equivalent codex mcp add command instead of editing it by hand.

~/.codex/config.toml

[mcp_servers.reloops]
command = "npx"
args = ["-y", "@reloops/mcp-server"]

[mcp_servers.reloops.env]
RELOOPS_API_KEY = "your_key_here"

Add this file, or type /mcp in the prompt panel to manage servers interactively.

~/.gemini/config/mcp_config.json

{
  "mcpServers": {
    "reloops": {
      "command": "npx",
      "args": ["-y", "@reloops/mcp-server"],
      "env": {
        "RELOOPS_API_KEY": "your_key_here"
      }
    }
  }
}

Add an MCP Client Tool node and connect it to an AI Agent node. Fill in these fields:

Field	Value
Connection Type	`Command Line (STDIO)`
Command	`npx`
Arguments	`-y @reloops/mcp-server`
Environment Variables	`RELOOPS_API_KEY=your_key_here`

Your agent can now call the same tools listed below from inside the workflow.

Any other MCP client that reads a JSON config file will use the same underlying command: npx -y @reloops/mcp-server, with RELOOPS_API_KEY set under env. Adjust the top-level key and file path for that client’s own format.

Validate

After connecting, ask your agent something like “List my Reloops workspaces” or “What’s still waiting on approval?”. A structured response back from your workspace confirms the connection is working.

Configuration reference

Environment variables the server reads, set under env in your client’s config:

Variable	Description	Required
`RELOOPS_API_KEY`	Your `reloops_live_…` developer key	Yes
`RELOOPS_API_BASE_URL`	Override the API base URL, for a non-default (e.g. self-hosted or staging) environment	No, defaults to `https://api.reloops.app/functions/v1`
`RELOOPS_MEDIA_BASE_URL`	Override the media/download base URL	No, defaults to `https://media.reloops.app`

Available tools

33 tools across workspaces, projects, assets, versions, comments, shares, and collections

Tool	Description
`reloops_list_workspaces`	List workspaces the API key can access
`reloops_create_workspace`	Create a new workspace
`reloops_list_projects`	List projects, optionally scoped to a workspace
`reloops_create_project`	Create a project in a workspace
`reloops_get_project_tree`	Get a project’s full folder/asset tree
`reloops_update_project`	Rename a project or set its status (Reloops has no hard project delete)
`reloops_list_folders`	List a project’s top-level folders
`reloops_create_folder`	Create a folder in a project
`reloops_delete_folder`	Delete a folder and everything inside it
`reloops_bulk_move_folders`	Move multiple folders to another project (same workspace)
`reloops_list_assets`	List assets by project, or list/search (keyword or semantic) by workspace
`reloops_get_asset`	Get one asset’s full details
`reloops_update_asset`	Update an asset’s status, metadata, folder, or assignment
`reloops_list_asset_versions`	List every version in an asset’s stack
`reloops_stack_asset_version`	Attach a standalone asset as a new version of another
`reloops_delete_asset`	Delete a single asset/version
`reloops_delete_asset_stack`	Delete an asset and every version stacked on it
`reloops_bulk_move_assets`	Move multiple asset stacks to another project (same workspace)
`reloops_bulk_copy_assets`	Copy multiple asset stacks to another project (same workspace)
`reloops_upload_asset`	Upload a local file as a new asset or new version
`reloops_download_asset`	Download an asset’s bytes to a local file
`reloops_list_comments`	List an asset’s review comments
`reloops_create_comment`	Leave a comment on an asset
`reloops_create_share`	Create a public share link for an asset or collection
`reloops_list_shares`	List existing share links
`reloops_revoke_share`	Revoke a share link
`reloops_list_assigned_reviews`	Poll the review queue assigned to this API key
`reloops_list_collections`	List saved collections in a workspace
`reloops_create_collection`	Create a filtered collection over a workspace/project/folder
`reloops_get_collection`	Get a collection’s saved configuration
`reloops_update_collection`	Rename or reconfigure a collection
`reloops_delete_collection`	Delete a collection (not its underlying assets)
`reloops_list_collection_items`	Resolve a collection’s filters and list its actual assets

Semantic search (reloops_list_assets with semantic: true) currently falls back to Reloops’ text-search behavior on the public API rather than true embedding search, that’s Reloops’ backend behavior, not a limitation of this tool.Not yet covered: multipart upload for files over 512 MiB, comment editing/deletion.

Troubleshooting

Tools not appearing in your client

Confirm the config file has valid JSON (or TOML for Codex CLI): a missing comma or brace stops the whole file from loading, not just the reloops entry.
Restart the client after editing its config. Most clients only read MCP config on startup.
Run npx -y @reloops/mcp-server directly in a terminal. If it hangs waiting on stdin without printing an error, the package installed and started correctly, the issue is in your client’s config, not the server.

Authentication or permission errors

Confirm RELOOPS_API_KEY is set in the env block for your client, not just in your shell, most clients launch the server as a separate process that doesn’t inherit your shell’s environment.
Check the key hasn’t been revoked: go to Manage Team → AI Agents & Developer Keys and confirm the agent is still listed.
Make sure the key is scoped to the workspace you’re asking about. A developer key only sees what its organization can access.

npx fails or can't find the package

Confirm Node.js is installed and npx is on your PATH (npx --version in a terminal).
The first run downloads the package fresh each time unless it’s cached. If you’re on a slow or restricted network, this can time out, try npm install -g @reloops/mcp-server and pointing command at the globally installed binary instead of npx.

Need a scriptable path instead of an agent? See Reloops CLI and Public API.

Get Started

Projects & Assets

AI & DAM

Collections

Review & Sharing

Workspace & Team

Developers & Agents

Guides

FAQ

Get a developer key

Connect your client

Validate

Configuration reference

Available tools

Troubleshooting

​Get a developer key

​Connect your client

​Validate

​Configuration reference

​Available tools

​Troubleshooting

Get a developer key

Connect your client

Validate

Configuration reference

Available tools

Troubleshooting