@zetaerp/f2c-mcp-bridge

Model Context Protocol (MCP) bridge connecting AI Coding Assistants (Google Antigravity, Claude Desktop, Cursor, Windsurf) directly to the Feedback 2 Code (F2C) Hub.

🌟 Features

• 📋 list_my_tasks: Fetches all active feedback tickets assigned to you and ready for AI implementation (ready_for_ai).
• 🔍 get_task_details: Retrieves full issue context including raw reporter descriptions, refined technical prompts, screenshots, and affected URL routes.
• ✅ resolve_task: Marks tickets as resolved directly from within your IDE, automatically providing summary feedback to client apps.

🚀 Quick Setup

1. Google Antigravity IDE

Add the following to your global MCP configuration at ~/.gemini/config/mcp_config.json (or inside your workspace .agents/mcp_config.json):

{
  "mcpServers": {
    "f2c-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@zetaerp/f2c-mcp-bridge"
      ],
      "env": {
        "F2C_HUB_URL": "https://f2c.zetaerp.net",
        "DEV_MCP_TOKEN": "YOUR_DEVELOPER_MCP_TOKEN"
      }
    }
  }
}

2. Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "f2c-hub": {
      "command": "npx",
      "args": [
        "-y",
        "@zetaerp/f2c-mcp-bridge"
      ],
      "env": {
        "F2C_HUB_URL": "https://f2c.zetaerp.net",
        "DEV_MCP_TOKEN": "YOUR_DEVELOPER_MCP_TOKEN"
      }
    }
  }
}

3. Cursor & Windsurf

In Cursor / Windsurf Settings > MCP Servers > Add New MCP Server:

• Name: f2c-hub
• Type: command
• Command: npx -y @zetaerp/f2c-mcp-bridge
• Environment Variables:
  • F2C_HUB_URL: https://f2c.zetaerp.net
  • DEV_MCP_TOKEN: YOUR_DEVELOPER_MCP_TOKEN

⚙️ Environment Variables

| Variable | Required | Default | Description | | :--- | :---: | :--- | :--- | | F2C_HUB_URL | Required | https://f2c.zetaerp.net | Base URL of your Feedback 2 Code (F2C) Hub instance | | DEV_MCP_TOKEN | Required | — | Personal Developer Token generated from the Feedback 2 Code (F2C) Dashboard |

🛠️ MCP Tools Overview

list_my_tasks

Lists all active tickets currently assigned to you and ready for AI implementation.

get_task_details

• Argument: ticket_id (UUID string)
• Returns: Full ticket details, technical prompt, client text, attachments, affected route URL, and reporter metadata.

resolve_task

• Arguments:
  • ticket_id (UUID string, required)
  • client_resolution_summary (string, required): Clear explanation of what was fixed or implemented to be displayed to the end-user.

📄 License

MIT © ZetaERP