Overview
Tools are persistent Docker containers that code agents connect to via MCP (Model Context Protocol). They run independently of agents — start once, use from any agent session.
Available Tools¶
| Tool | Purpose | MCP Endpoint | Port |
|---|---|---|---|
| Chrome | Headless browser automation via CDP | http://127.0.0.1:9223/mcp |
9222 (CDP), 9223 (MCP) |
| Web | Web search and page fetching via Camoufox | http://127.0.0.1:8420/mcp |
8420 |
| GitHub | GitHub API access (repos, issues, PRs) | http://127.0.0.1:8129/mcp |
8129 |
| Web Bridge | SearXNG bridge for LiteLLM web search interception | http://127.0.0.1:8500/search |
8500 |
Manage All Tools¶
cf run tools start # Start all tools
cf run tools stop # Stop all tools
cf run tools restart # Restart all tools
cf run tools status # Show status
Short aliases:
How Tools Connect to Agents¶
When you launch an agent (cf r ag cc), CodeFreedom:
- Reads the agent profile's
toolslist (e.g.,[chrome, web, github]) - Ensures each tool's Docker container is running
- Builds an MCP server config pointing to each tool's endpoint
- Writes the config to the agent's workspace (e.g.,
.mcp.jsonfor Claude Code)
The agent sees tools as native MCP servers. No manual wiring needed.
Tool Profiles¶
Each tool's config lives in ~/.codefreedom/profiles/<tool>.yaml:
chrome:
image: docker.io/nilayparikh/codefreedom:chrome-latest
container_name: codefreedom-tools-chrome
port: 9222
mcp_port: 9223
mcp_path: /mcp
env:
CHROME_DEBUG_PORT: '9222'
MCP_PORT: '9223'
Profiles are deployed by recipes. Use cf s i to initialize.
Data Directories¶
Each tool stores persistent data under ~/.codefreedom/tools/<tool>/:
~/.codefreedom/tools/
├── chrome/ # Chrome profile, cookies, extensions
├── web/ # Camoufox profile data
├── github/ # GitHub MCP cache
└── web-bridge/ # Bridge state
Third-Party Notices¶
Each tool container includes third-party components. CodeFreedom is not responsible for their behavior, security, or privacy practices. See individual tool pages for details.