freeproxy is an open-source, local-first proxy rota for AI agents. Run it on devices you own or administer, expose local HTTP/SOCKS5 and MCP interfaces, and route requests through explicit policy over a private mesh. Logs and configuration stay local unless you export them.
The open web was built on the principle that any user could reach any page.
Agents need network access, but the default choices are usually a shared cloud proxy or no policy at all.
Your devices already sit in trust zones you understand: home, office, mobile, lab, server.
freeproxy lets you expose those approved paths to your own agents with scoped keys, route policy, SSRF protections, and local observability.
The goal is not stealth or challenge bypass. It is user-owned routing with explicit controls.
Run the daemon on a laptop, a Raspberry Pi at home, a mini PC on mobile broadband, or a VPS you administer. Nodes join through tsnet today; Headscale and other transports are designed as follow-ons.
Round-robin. Sticky-by-domain. Least-loaded. Fastest. Deny. Tag nodes as home, work, mobile, or trusted and keep route decisions explicit.
HTTP/SOCKS5 proxy on localhost:7777, or speak MCP directly. Works with Claude Desktop, Cursor, Cline, custom Python — anything that can use a proxy or call a tool.
Tunnel rows show host, node, agent, bytes, duration, and error class. MCP fetch rows can include HTTP status because freeproxy performs that request directly. Logs stay local; exports are explicit.
Apache 2.0. Audit the binary, fork the protocol, run the whole stack on your own metal. No mandatory cloud.
Not a freemium tier waiting to be metered. The right framing is civic, not commercial: your access, extended.
Your home fiber, lab box, mobile uplink, or VPS. Existing connections become explicitly tagged routes for your agents.
Every request is evaluated against your route table before a node is selected. Deny rules never dispatch.
Native Model Context Protocol server. Current tools: fetch, choose_node, and list_nodes. Crawler/session tools stay gated for later releases.
Tailscale tsnet is the default transport. Headscale is planned next; Cloudflare-style mesh is opt-in only because it changes metadata visibility.
No central proxy. No shared exit pool. No telemetry. Logs are local-first; export only if you say so.
One control plane, many trust zones. Tag nodes home, work, school, mobile and route by tag.
Designed for headless workloads: long-lived sessions, structured retries, deterministic IP selection, programmable from the agent side.
registered nodes · scoped keys · route policy · local traffic log
The first key should usually be created with the CLI before leaving the daemon running.
curl -fsSL https://freeproxy.app/install.sh | sh freeproxy keys create --label claude \ --scopes proxy:use,mcp:fetch,mcp:list_nodes,mcp:choose_node freeproxy up
Rules are evaluated top-to-bottom. Deny rules stop before dispatch; hostname rules require the proxy to see a hostname.
[[route]] name = "research" hosts = ["arxiv.org", "docs.python.org"] strategy = "sticky-by-domain" node_tags = ["home", "trusted"] [[route]] name = "blocked" hosts = ["social.example"] strategy = "deny"
Joined nodes register through the coordinator admin API, then node-agent health checks decide whether they stay eligible for policy selection.
freeproxy join create \ --label mobile-uplink \ --tags mobile,trusted \ --coord-admin-url http://100.x.y.z:7776 freeproxy join FP-....-....
Admin, proxy, and MCP calls use scoped keys. Mesh dispatch uses a separate node-agent token. SSRF protections block loopback, private ranges, metadata IPs, and local names by default.
fetch records status because freeproxy performs the request.M0 through M6 are implemented and verified. Current release artifacts are Linux amd64 tarball and deb; Docker scaffolding is present; macOS and Homebrew are planned.
freeproxy version freeproxy status freeproxy keys list curl -H "Authorization: Bearer $FP_KEY" \ http://127.0.0.1:7776/api/traffic?format=csv
The curl installer is for ad-hoc/dev use. For systemd-managed Linux hosts, use the deb so the service file and package layout match.
# ad-hoc curl -fsSL https://freeproxy.app/install.sh | sh # managed host sudo dpkg -i freeproxy_*.deb
{
"mcpServers": {
"freeproxy": {
"command": "freeproxy",
"args": ["mcp"],
"env": {
"FP_KEY": "fp_live_••••••••••••"
}
}
}
}
// exposes tools: fetch, choose_node, list_nodes
# http proxy on localhost:7777 curl -x http://127.0.0.1:7777 \ -H "Proxy-Authorization: Bearer fp_live_••••" \ -H "X-FP-Policy: round-robin" \ https://example.com
# socks5 proxy on localhost:7778 curl --socks5 127.0.0.1:7778 \ --proxy-user "agent:fp_live_••••" \ https://example.com
Drop the snippet into Claude Desktop, Cursor, Cline, or any MCP-aware client. Your agent gets policy-aware fetches and node introspection without leaving your local control plane.
Fetches one absolute HTTP or HTTPS URL through route policy, rate limits, SSRF protections, and the selected node.
{
"url": "https://example.com",
"method": "GET",
"headers": { "accept": "text/html" }
}
Returns status_code, response headers, body text, bytes down, duration, retry count, and node id.
Selects a registered node by name/id or by a required tag set, using the local node table.
{
"tags": ["mobile", "trusted"]
}
Useful when an agent should decide whether a route is available before issuing a fetch.
Returns the coordinator's current view of registered nodes, tags, health, load score, and source.
{}
Agents can inspect available exits without receiving direct mesh credentials.