# flanner

flanner keeps AI agent plans in one managed folder, tracks revisions, and exposes their history. Use it for architecture notes and migration plans.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 5
- Author: elandlabs
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/elandlabs/flanner
- Updated: 2026-10-08
- HTML: https://affpapa.org/en/nevibecode/mcp/flanner

## What it does

flanner exposes MCP tools for working with agent plans. Each plan receives YAML metadata, while every revision becomes a separate version with a history. Plans live in `.plans/`, and `flanner init` updates `.gitignore`, creates project configuration, and adds integration blocks to `CLAUDE.md` and `AGENTS.md`.

A local browser view lets you read and edit plans and walk through their revisions. Start it with `flanner web --open-browser`; the interface opens at `http://localhost:8080`. The server also keeps durable plan context as Markdown files and can inspect installed skills and an agent’s access to secrets. `flanner-mcp` must be available on `PATH` because the agent launches it by name.

Linear and JIRA links are disabled in this build. Enabling them requires `FLANNER_INTEGRATIONS=1`, while Linear issue checks use `LINEAR_API_KEY`.

## Requirements
- Needs: Python and uv (commands run via uvx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add flanner -- uvx flanner
```
uvx runs the command named after the package; if the README names another one, use uvx --from flanner <command>

### Codex

**Platform CLI**
```bash
codex mcp add flanner -- uvx flanner
```
uvx runs the command named after the package; if the README names another one, use uvx --from flanner <command>

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "flanner": {
            "command": "uvx",
            "args": [
                "flanner"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from flanner <command>

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "flanner": {
            "type": "stdio",
            "command": "uvx",
            "args": [
                "flanner"
            ]
        }
    }
}
```
uvx runs the command named after the package; if the README names another one, use uvx --from flanner <command>

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add flanner uvx flanner
```
uvx runs the command named after the package; if the README names another one, use uvx --from flanner <command>

## When to use it
- keep agent plans under `.plans/`
- track revisions of an architecture plan
- connect a plan to a Linear or JIRA issue
- browse plan history in a local web view
- inspect loaded skills and agent access to secrets

## Example prompts
- Create an architecture plan for the authentication service and save it through flanner.
- Show me the revision history for the architecture plan.
- Check which skills are loaded and which copy is active.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 392262
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33989
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81163
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119231
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47577
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43902

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md