fde-mission-control-mcp

An MCP (Model Context Protocol) server for IBM Client Engineering FDE Mission Control. Connects any MCP-compatible AI assistant (Bob, GitHub Copilot, Cursor, etc.) to your Mission Control instance, exposing project-request and engagement management APIs as callable tools.

Prerequisites

• Node.js 18 or later
• Access to an FDE Mission Control instance
• An API Key (Personal Access Token starting with sk_...) generated in Developer Settings

Installation

Option A — npx (recommended, no install required)

Add the following to your MCP client config (e.g. .bob/mcp.json for Bob, .vscode/mcp.json for GitHub Copilot in VS Code (using "servers" key), ~/.cursor/mcp.json for Cursor):

{
  "mcpServers": {
    "fde-mission-control": {
      "command": "npx",
      "args": ["-y", "fde-mission-control-mcp"],
      "env": {
        "FDE_API_BASE": "https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud",
        "FDE_API_KEY": "sk_yourTokenHere"
      }
    }
  }
}

Option B — global install

npm install -g fde-mission-control-mcp

Then configure your MCP client:

{
  "mcpServers": {
    "fde-mission-control": {
      "command": "fde-mission-control-mcp",
      "args": [],
      "env": {
        "FDE_API_BASE": "https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud",
        "FDE_API_KEY": "sk_yourTokenHere"
      }
    }
  }
}

Option C — build from source

git clone https://github.com/ibm-client-engineering/fde-mission-control-mcp.git
cd fde-mission-control-mcp
npm install
npm run build

Then point your MCP client configuration at the compiled entry point (build/index.js):

{
  "mcpServers": {
    "fde-mission-control": {
      "command": "node",
      "args": ["/absolute/path/to/fde-mission-control-mcp/build/index.js"],
      "env": {
        "FDE_API_BASE": "https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud",
        "FDE_API_KEY": "sk_yourTokenHere"
      }
    }
  }
}

Configuration

| Environment variable | Required | Default | Description | |---|---|---|---| | FDE_API_BASE | ✅ | — | Base URL of your FDE Mission Control instance. Trailing /api or / is stripped automatically. | | FDE_API_KEY | ✅ | — | Personal access token starting with sk_... generated in the portal UI (Profile Picture → Developer Settings). |

FDE_API_BASE values

| Environment | Base URL | |---|---| | Production | https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud | | UAT | https://fde-mission-control-uat.29dozlgcwo29.us-south.codeengine.appdomain.cloud | | Local dev | http://localhost:8000 |

How to get your API key

1. Log in to the FDE Mission Control portal.
2. Click your profile picture (avatar) in the top navigation / menu.
3. Select Developer Settings.
4. Generate a new personal access token (starts with sk_...) and copy it.
5. Set the token as FDE_API_KEY in your MCP client configuration.

Available tools

Projects & Engagements

| Tool | Parameters | Description | |---|---|---| | list-my-projects | — | List active project assignments for the authenticated FDE. Returns a compact list including request_id, client_name, project_name, stage, health, days_in_stage, is_urgent, is_priority, and is_troubled_project. Use request_id for other project tools. | | get-project | request_id (integer, required) | Full engagement detail for a single project: stage, health, client name, project name, market, engagement owner email, FDE team members, core solutions, opportunity status, urgency/priority flags, open blockers & risks counts, and latest status update snippet. |

Development

git clone https://github.com/ibm-client-engineering/fde-mission-control-mcp.git
cd fde-mission-control-mcp
npm install
npm run build        # compiles src/index.ts → build/index.js
npm run dev          # watch mode

To test locally with the MCP Inspector:

On macOS / Linux:

cp inspector-config.json.sample inspector-config.json
# Edit inspector-config.json with your FDE_API_BASE and FDE_API_KEY
npx @modelcontextprotocol/inspector --config inspector-config.json

Or run inspector directly with environment variables:

On Windows (PowerShell):

$env:FDE_API_BASE="https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud"
$env:FDE_API_KEY="sk_yourTokenHere"
npx @modelcontextprotocol/inspector node build/index.js

On macOS / Linux:

FDE_API_BASE="https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud" \
FDE_API_KEY="sk_yourTokenHere" \
npx @modelcontextprotocol/inspector node build/index.js

Testing directly inside Bob (IBM Bob IDE)

The repository includes a .bob/mcp.json.sample template. Copy it to .bob/mcp.json, configure your credentials, and Bob will register the MCP server automatically.

.bob/mcp.json is listed in .gitignore so your credentials are never tracked by git.

Setup steps:

1. Copy the sample configuration:

   On Windows (PowerShell):

   Copy-Item .bob/mcp.json.sample .bob/mcp.json

   On macOS / Linux:

   cp .bob/mcp.json.sample .bob/mcp.json

2. Open .bob/mcp.json and fill in your values:

   Note: Ensure there are no comment lines (//) in .bob/mcp.json, as invalid JSON comments will prevent Bob from loading the server.

   • FDE_API_BASE → your Mission Control base URL
   • FDE_API_KEY → your personal access token (sk_...)

3. Run npm run build (or npm run dev for watch mode) to build the project.

4. Open the MCP panel in Bob and confirm the fde-mission-control server is connected and its tools are available.

Troubleshooting the Bob MCP connection

1. Confirm the build exists

On Windows (PowerShell):

Test-Path build/index.js

On macOS / Linux:

ls build/index.js

If missing, run npm run build first.

2. Run the server manually

The server communicates over stdio. A clean start will block silently waiting for input. Any error output before that indicates a configuration or runtime issue.

On Windows (PowerShell):

$env:FDE_API_BASE="https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud"
$env:FDE_API_KEY="sk_yourTokenHere"
node build/index.js

On macOS / Linux:

FDE_API_BASE="https://fde-mission-control.29dozlgcwo29.us-south.codeengine.appdomain.cloud" \
FDE_API_KEY="sk_yourTokenHere" \
node build/index.js

3. Check the Bob MCP logs

• Open View → Output in Bob.
• Select IBM Bob MCP from the dropdown menu to stream live logs.

Releasing a new version

1. Make and test your changes

2. Run npm run build to confirm it compiles cleanly

3. Bump the version and create the git tag:

   npm version patch   # bug fix:        2.0.0 → 2.0.1
   npm version minor   # new tools:      2.0.0 → 2.1.0
   npm version major   # breaking change: 2.0.0 → 3.0.0

4. Push the commit and tag:

   git push --follow-tags

The GitHub Actions workflow triggers automatically on tag push (v*), compiles the package, and publishes to npm.

License

MIT