MCP Integration

Learn how Flanner integrates with Claude Code through the Model Context Protocol (MCP) to provide seamless plan file management.

Overview

Flanner features automatic Claude Code integration! The MCP server is automatically registered with Claude Code when you run flanner init, making it seamless to use plan file management directly from Claude.

Features

Automatic Registration

• ✅ Auto-detect Claude Code installation
• ✅ Auto-configure MCP server settings
• ✅ Auto-update configuration if paths change
• ✅ Verify registration on every status check

Manual Control

• 🔧 Register/unregister at any time
• 🔧 Force update configuration
• 🔧 View detailed integration status
• 🔧 Support for future cloud-based servers

Quick Setup

1. Initialize (Auto-Registration)

# Run init - MCP server is automatically registered! flanner init

Output includes:

✓ Initialized Flanner... 🔌 Registering MCP server with Claude Code... ✓ MCP server registered in Claude Code You may need to restart Claude Code for changes to take effect

2. Verify Registration

flanner status

Shows:

------------------------------------------------------------ CLAUDE CODE INTEGRATION ------------------------------------------------------------ Config Path: C:\Users\...\Claude\claude_desktop_config.json MCP Server: Registered & Valid

3. View Detailed Info

flanner claude-info

Shows complete details including configuration file location, registration status, and current server configuration.

4. Restart Claude Code

After registration, restart Claude Code to load the MCP server.

5. Test with Claude

Ask Claude to interact with the plan manager:

User: "List all my projects in the plan manager" User: "Create a new architecture plan for my current project" User: "Show me the version history of the architecture plan"

Available MCP Tools

Flanner exposes the following tools to Claude through MCP:

get_plan_config()

Get configuration for creating plan files.

list_projects()

List all projects.

create_project_tool()

Create a new project.

list_plan_files()

List plan files for a project.

create_plan_file_tool()

Create a new plan file with automatic frontmatter.

update_plan_file_tool()

Update a plan file and create a new version.

get_plan_history_tool()

Get version history for a plan file.

JIRA Tools

• configure_jira_tool() - Configure JIRA for a project
• link_plan_to_jira_tool() - Link plan to JIRA issue
• get_jira_links_tool() - Get JIRA links for a plan
• list_jira_links_tool() - List all JIRA links
• unlink_jira_issue_tool() - Unlink JIRA issues
• get_jira_config_tool() - Get JIRA configuration

Configuration File Location

The CLI automatically detects Claude Code's configuration file:

Windows

C:\Users\YourName\AppData\Roaming\Claude\claude_desktop_config.json

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Linux

~/.config/claude/claude_desktop_config.json

How It Works

On init Command

1. Check if MCP server is already registered
2. Verify configuration is correct if registered
3. Update configuration if paths changed
4. Register if missing
5. Notify user of next steps

On status Command

1. Check if server is registered
2. Validate current configuration matches expected
3. Show action needed if not registered or outdated

Configuration Structure

{
  "mcpServers": {
    "flanner-manager": {
      "command": "python",
      "args": [
        "-m",
        "src.server"
      ],
      "cwd": "C:\\path\\to\\flanner",
      "env": {}
    }
  }
}

Manual Registration

Register MCP Server

# If auto-registration failed or was skipped flanner register # Force update configuration flanner register --force # Skip Claude integration during init flanner init --skip-claude

Unregister

# Remove MCP server from Claude Code flanner unregister

Troubleshooting

Could not find Claude Code configuration path

Solution:

• Ensure Claude Code is installed
• Check if configuration file exists
• Try manual registration

MCP server registered but not working in Claude

Solutions:

1. Restart Claude Code completely
2. Check Claude Code's MCP settings UI
3. Run flanner claude-info to verify configuration
4. Re-register with flanner register --force

Configuration path is different

Edit src/claude_integration.py and add your custom path.

Use Cases

First Installation

pip install -r requirements.txt flanner init # ✓ MCP server automatically registered # ✓ Ready to use with Claude immediately

Moved Project Directory

# You moved the flanner folder flanner init # ✓ Configuration automatically updated with new path

Multiple Developers

# Each developer runs init on their machine flanner init # ✓ Each gets correct path for their system # ✓ No manual configuration needed

Status Indicators

Registered & Valid (Green)

• ✅ MCP server is registered
• ✅ Configuration is correct
• ✅ No action needed

Registered (config outdated) (Yellow)

• ⚠️ MCP server is registered
• ⚠️ Configuration has changed
• 💡 Run flanner init to update

Not Registered (Yellow)

• ⚠️ MCP server not found in Claude config
• 💡 Run flanner init or flanner register