Skip to main content
CodeFire integrates seamlessly with all major AI coding CLIs through its MCP server. This guide walks through setting up each CLI tool.

​
Overview

CodeFire exposes your project data (tasks, notes, sessions, file tree) to AI coding tools via the CodeFireMCP server. Once configured, your AI agent has persistent memory and awareness of your work across sessions. The MCP server binary is located at: 
~/Library/Application Support/CodeFire/bin/CodeFireMCP

​
Supported CLIs

1
Claude Code
2
The easiest way to connect Claude Code is using the one-click installer in CodeFire. Alternatively, configure manually:
3
claude mcp add codefire ~/Library/Application\ Support/CodeFire/bin/CodeFireMCP
4
This registers the MCP server in your Claude Code configuration (~/.claude/mcp.json).
5
Verify the installation:
6
claude mcp list
7
You should see codefire in the list of configured servers.
8
Gemini CLI
9
Add the MCP server to your Gemini CLI settings file:
10
// ~/.gemini/settings.json
{
  "mcpServers": {
    "codefire": {
      "command": "~/Library/Application Support/CodeFire/bin/CodeFireMCP",
      "args": []
    }
  }
}
11
Test the connection: Start a Gemini session and verify MCP tools are available:
12
gemini "list available tools"
13
Codex CLI
14
Edit your Codex configuration file:
15
# ~/.codex/config.toml
[mcp_servers.codefire]
command = "~/Library/Application Support/CodeFire/bin/CodeFireMCP"
args = []
16
Restart any active Codex sessions to load the new configuration.
17
OpenCode
18
Add CodeFire to your OpenCode MCP servers:
19
// ~/.opencode/config.json
{
  "mcpServers": {
    "codefire": {
      "command": "~/Library/Application Support/CodeFire/bin/CodeFireMCP",
      "args": []
    }
  }
}
20
Verify:
21
opencode "show me the project tasks"

​
Auto-Discovery of Projects

CodeFire automatically discovers all your Claude Code projects by scanning ~/.claude/projects/. Each project directory name is decoded to resolve the original filesystem path.

​
How Project Discovery Works

  1. Scan ~/.claude/projects/ — CodeFire reads all directories in this folder
  2. Decode directory names — Claude encodes absolute paths by replacing /, , ., and - with -. CodeFire uses a backtracking algorithm to resolve the ambiguous encoding back to the original path
  3. Import sessions — For each project, CodeFire indexes all .jsonl session files and parses token usage, tool invocations, and files changed
  4. Update database — All projects and sessions are stored in ~/Library/Application Support/CodeFire/codefire.db
Manual refresh: CodeFire re-scans on startup, but you can trigger a manual refresh from the home view (click the refresh icon in the toolbar).

​
Supported Project Structures

CodeFire works with any project structure that Claude Code supports. It detects:
  • Package managers (npm, yarn, pnpm, bun, pip, poetry, cargo, etc.)
  • Git repositories and branches
  • Framework types (Next.js, React, Vue, Python, Rust, etc.)
  • Build and test commands

​
Troubleshooting

​
MCP Server Not Found

Symptom: CLI reports “codefire server not found” or “command not found” Solution:
  1. Verify the binary exists: 
    ls -la ~/Library/Application\ Support/CodeFire/bin/CodeFireMCP
  2. Ensure it’s executable: 
    chmod +x ~/Library/Application\ Support/CodeFire/bin/CodeFireMCP
  3. Check your CLI config file has the correct path with proper escaping

​
Projects Not Auto-Discovered

Symptom: CodeFire home view shows no projects Solution:
  1. Verify ~/.claude/projects/ exists and contains project directories: 
    ls ~/.claude/projects/
  2. Open CodeFire settings (Cmd+,) → CodeFire Engine → toggle “MCP server auto-start”
  3. Restart CodeFire
  4. If projects still don’t appear, check that the project directories haven’t been deleted from disk

​
CLI Can’t Connect to MCP Server

Symptom: CLI starts but MCP tools aren’t available Solution:
  1. Check CodeFire is running (the app must be open for the MCP server to respond)
  2. Restart your CLI session
  3. Check the MCP server logs in CodeFire (Settings → CodeFire Engine → View Logs)
  4. Ensure no other process is using the same MCP server name

​
Session Data Not Updating

Symptom: New Claude Code sessions don’t appear in CodeFire Solution:
  1. CodeFire watches .jsonl files with a 5-second debounce. Wait a few seconds after your session ends
  2. Check Settings → CodeFire Engine → “Auto-snapshot sessions” is enabled
  3. Manually refresh the sessions view (click the refresh icon)
  4. Verify the .jsonl file exists in ~/.claude/projects/<your-project>/

​
Next Steps

Gmail Integration

Sync emails to auto-create tasks

Workflows

Common workflows and best practices

Build docs developers (and LLMs) love

Get started for freeTalk to us