How do I install FrelyMCP?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does FrelyMCP need an API key?

No required environment variable is listed on this record.

When was FrelyMCP last checked?

Last checked 2026-11-10. Use your own computers, cloud tools and AI agents from any MCP client with one Frely login.

FrelyMCP MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.frely.cloud/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http cloud.frely-frelymcp https://mcp.frely.cloud/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "cloud.frely-frelymcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.frely.cloud/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 1.1.1
License

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Frely CLI

Website · Docs · Frely · English · 简体中文

Frely CLI (frely-cli) connects a computer you choose to FrelyMCP, so ChatGPT, Claude, Codex and other MCP clients can work on it from anywhere. They use the files, shell commands and processes in the folders you allow. The computer connects out to Frely, so you open no ports.

It is also the command line for your Frely account:

Device MCP: let remote AI clients work on this computer.
Local MCP servers: pass MCP servers that only run on this computer (for example on 127.0.0.1) through to remote clients.
Agents, Prompts and Skills: install a published Frely Agent as a local Skill, or install Prompts and Skills you bought.
Local model sharing: publish a local Ollama or OpenAI-compatible runtime as your own Frely Provider.

Install

A server, with a Frely account (no browser)

Get a one-time install command on the Frely website (My Devices → Add a computer → Create install command), or ask ChatGPT or Claude connected to FrelyMCP to add a computer. Paste it on the server:

curl -fsSL https://frely.cloud/start.sh | FRELY_INSTALL_TOKEN=fit_... sh

It installs frely, signs in to your account, enables Device MCP and starts the background service. The token works once and expires after 15 minutes. On Linux, run sudo loginctl enable-linger $USER so the service stays online after you log out of SSH. More

A computer with a browser

# macOS / Linux
curl -fsSL https://frely.cloud/start.sh | sh

# Windows (PowerShell)
curl.exe -fsSLo "$env:TEMP\frely-start.ps1" https://frely.cloud/start.ps1; powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\frely-start.ps1"

The script installs the latest frely, opens the browser to sign in (new accounts can register there), asks you to approve this device and prints your MCP URL. Run it again any time to update. The workspace is your home directory by default; set FRELY_WORKSPACE=/path to share another folder. More

Let your agent set it up

Ask an agent that has a shell (Claude Code, Codex, pi) to install the CLI, sign in with frely login --email, and run frely skill install --host <host>. The frely Skill teaches the agent to use your account and to offer FrelyMCP only when a request needs it. This path does not open this computer to remote clients; frely mcp start does.

Install only

https://frely.cloud/install.sh and install.ps1 only install the program, for scripts and agents that need the CLI. Or use npm (Node.js 22 or newer):

npm install --global --ignore-scripts frely-cli@latest

The installers check the SHA-256 and download from GitHub Releases first, then npmmirror and npmjs. More

Common commands

Command	What it does
`frely mcp start`	Sign in if needed, enable Device MCP, start the service and print the MCP URL. Safe to re-run.
`frely mcp status`	Show the MCP URL, workspace, authorization expiry and service state.
`frely mcp workspace add <path>`	Share another folder. `frely mcp workspace list` shows them all.
`frely mcp stop` / `frely mcp start`	Pause or resume the background service.
`frely mcp auto-update [on\|off]`	Let the background service update itself while idle (macOS/Linux, off by default).
`frely mcp remove`	Revoke access for every client and uninstall the service.
`frely doctor`	Check sign-in, installation, service and connection. `-v` for details.
`frely update`	Update to the latest version in place.
`frely login` / `frely logout`	Sign in or out of your Frely account.
`frely sandbox proxy <url>`	Forward the command sandbox's network traffic to your own HTTP(S) proxy. Without it the CLI uses `HTTPS_PROXY` / `HTTP_PROXY` / `ALL_PROXY` and, on macOS, the system proxy. `--clear` removes it; restart the service to apply.
`frely tunnel <host>:<port>`	Inside a sandboxed command: listen on `127.0.0.1` and forward TCP connections to `host:port` through the sandbox, for database and redis clients. `--local-port N` picks the local port.
`frely uninstall`	Remove Frely from this computer (lists everything first).

All commands and options: command reference. frely help --agent --json prints the full machine-readable contract.

Use with FrelyMCP

FrelyMCP is one MCP address for your whole account: https://mcp.frely.cloud/mcp. Every computer where you ran frely mcp start appears behind it.

On the computer to control, run frely mcp start (the install scripts above already do this).
Add the URL to your client as a remote MCP server with OAuth:
- ChatGPT or Claude: add a custom connector with the URL.
- Claude Code on another computer: claude mcp add --transport http frely "https://mcp.frely.cloud/mcp", then open /mcp to authorize.
Sign in to Frely and approve the client.

To check the connection, ask the client to list the top-level names in your workspace.

What the AI can do: list_devices, then read, edit_file, process and web_fetch on the computer you pick, plus your account through frely_list and frely_call. More
Local MCP servers: loopback servers are found automatically (frely mcp local list); each stays hidden until you turn it on in Frely. More
Authorization: access lasts 90 days by default; frely mcp start --days 1..365 renews early. The URL never changes. More

More features

Agents on this computer: frely agent local add <username/name> downloads an Agent's repository into its own folder and frely agent local start <name> runs it inside the Frely sandbox. It can write only that folder, cannot read your SSH or cloud credentials, and never sees your Frely API key; its model calls go through a local proxy that adds the key. It can reach Frely's API and, after you approve each one once, the sites its frely.yaml lists. Details
Frely-hosted Agents: frely item install <username/name> --host claude-code installs an Agent as a local Skill; frely agent run <username/name> calls it. More
Marketplace Prompts and Skills: frely item install <username/name> --host claude-code (the same command installs Agents too; add @3 for version 3). Paid parts install only when your account holds a pass. frely item update lists installed items that have a newer version; it changes nothing until you run frely item update <folder>. More
Local model sharing: frely provider share ollama publishes a loopback model server as your personal Frely Provider. More
Share a local web page: frely share 3000 asks first, then prints a private link to http://127.0.0.1:3000 through Frely's relay until you press Ctrl+C or it expires (at most 24 hours). Relay traffic is a plan allowance per UTC week; direct connections are not counted. Not the same as frely provider share (local models) or frely tunnel (inside the command sandbox).
Your account from the terminal: frely api list|describe|call. More

Safety

File tools stay inside the shared workspaces and protect credential and shell start-up files. Commands run as your OS user inside an OS sandbox, and are refused where the computer cannot sandbox them. Clients hold OAuth tokens; the CLI keeps its own key in the system credential store. Is it safe? · Sandbox and permissions · Credential storage

Documentation

Help: cli.frely.cloud/docs (update, doctor, uninstall)
Contracts, for contributors: Device MCP · Device Relay transport · MCP OAuth contract · frely api · Frely Network (preview) · self-update · service maintenance

License and trademarks

frely-cli is licensed under the Apache License 2.0; see LICENSE. The Frely name, logos and product names are not licensed as trademarks; see TRADEMARKS.md. See CONTRIBUTING.md for development and SECURITY.md to report a vulnerability.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install FrelyMCP?

Does FrelyMCP need an API key?

What transport does FrelyMCP use?

When was FrelyMCP last checked?

Documentation

Frely CLI

Install

A server, with a Frely account (no browser)

A computer with a browser

Let your agent set it up

Install only

Common commands

Use with FrelyMCP

More features

Safety

Documentation

License and trademarks