Skip to main content

Sitemule Blueprint MCP Server

A Model Context Protocol (MCP) server for IBM i program analysis, built with FastMCP.

⚠️ Prerequisite: This MCP server requires a licensed copy of Sitemule Blueprint running on an IBM i server. Without it, there is no backend to connect to. Contact Sitemule for licensing information.

Features

  • STDIO and Streamable HTTP transports
  • IBM i program call-chain analysis (top-down & bottom-up)
  • Source code retrieval and regex search
  • Configurable API endpoint and API key (key is never exposed to the LLM)
  • Packaged for PyPI via uv
  • Self-contained executables for Windows, macOS, and Linux

Tools

The MCP server exposes 6 tools for IBM i program analysis. Configuration management (getConfig, setConfig) and graph rebuilds (loadGraph) are handled by the companion VS Code extension — see VS Code Extension below.

Read-only

Tool Description
get_graph_top_down Forward call/dependency chain: all programs and data-entities this node interacts with
get_graph_bottom_up Reverse call chain / impact analysis: all programs and data-entities that interact with this node
get_program_info Metadata and description for a program or table (no source code)
get_program_source Source code and source-file location for a program or table
search_source_code_with_regex Search program source and table definitions for text matching a regular expression
get_domains List all defined domains, including a 'No domain' entry for unassigned nodes

Installation

From PyPI

# Install with uv
uv pip install blueprint-mcp

# Or with pip
pip install blueprint-mcp

From source

git clone https://sitemule.dev/sitemule/blueprint-mcp.git
cd blueprint-mcp
uv sync

VS Code Extension

The companion Sitemule Blueprint extension (in src/vscode/blueprint-mcp-settings/) provides a Settings UI and manages server communication directly:

Command Description
Blueprint: Refresh Settings from Server Fetch current config via getConfig and populate VS Code settings
Blueprint: Save Settings to Server Push VS Code settings to the backend via setConfig
Blueprint: Rebuild Dependency Graph Trigger loadGraph to re-scan the IBM i
Blueprint: Save Settings & Rebuild Graph Save config then rebuild in one step
Blueprint: Generate mcp.json Write .vscode/mcp.json to register the MCP server

Workflow:

  1. Set blueprint.apiUrl (and optionally blueprint.apiKey) in VS Code settings
  2. The extension fetches the current config from the backend on activation
  3. Edit any setting — changes are automatically pushed to the backend
  4. Use the command palette to rebuild the graph when ready

The extension also generates .vscode/mcp.json automatically so VS Code can launch the MCP server with the correct API credentials.

Configuration

All configuration is via environment variables:

Variable Required Default Description
BLUEPRINT_API_URL Yes http://MY_IBM_I:7111/services/api Base URL for the Blueprint API
BLUEPRINT_API_KEY No (none) API key sent as Authorization: Bearer <key> header. Never exposed to the LLM.
BLUEPRINT_HOST No 0.0.0.0 Host for HTTP transport
BLUEPRINT_PORT No 8000 Port for HTTP transport

Usage

STDIO (default — for IDE integrations like VS Code, Cursor, etc.)

BLUEPRINT_API_URL=http://ibm-i.host.or.ip:7111/services/api blueprint-mcp

Streamable HTTP

BLUEPRINT_API_URL=http://ibm-i.host.or.ip:7111/services/api blueprint-mcp --transport streamable-http

With API key

BLUEPRINT_API_URL=http://ibm-i.host.or.ip:7111/services/api \
BLUEPRINT_API_KEY=my-secret-key \
blueprint-mcp --transport streamable-http --port 9000

MCP client configuration (e.g. Claude Desktop, VS Code)

{
  "mcpServers": {
    "blueprint": {
      "command": "blueprint-mcp",
      "env": {
        "BLUEPRINT_API_URL": "http://ibm-i.host.or.ip:7111/services/api",
        "BLUEPRINT_API_KEY": "my-secret-key"
      }
    }
  }
}

VS Code — one-click install from MCP Registry

  1. Open the command palette (Ctrl+Shift+P / Cmd+Shift+P)
  2. Run MCP: Add Server… → search for Sitemule Blueprint
  3. VS Code will prompt you for the API URL and (optionally) the API key
  4. Settings are stored securely — the API key is never exposed to the LLM

Or add a .vscode/mcp.json file to your workspace manually:

{
  "inputs": [
    {
      "id": "blueprint-api-url",
      "type": "promptString",
      "description": "Blueprint API URL (e.g., http://ibm-i.host.or.ip:7111/services/api)",
      "default": "http://ibm-i.host.or.ip:7111/services/api"
    },
    {
      "id": "blueprint-api-key",
      "type": "promptString",
      "description": "Blueprint API Key (leave empty if not required)",
      "default": "",
      "password": true
    }
  ],
  "servers": {
    "blueprint": {
      "type": "stdio",
      "command": "blueprint-mcp",
      "args": ["--transport", "stdio"],
      "env": {
        "BLUEPRINT_API_URL": "${input:blueprint-api-url}",
        "BLUEPRINT_API_KEY": "${input:blueprint-api-key}"
      }
    }
  }
}

Self-contained executable

Download the pre-built executable for your platform from Releases and run it directly — no Python installation required:

# Linux / macOS
chmod +x blueprint-mcp-linux
BLUEPRINT_API_URL=http://ibm-i.host.or.ip:7111/services/api ./blueprint-mcp-linux

# Windows
set BLUEPRINT_API_URL=http://ibm-i.host.or.ip:7111/services/api
blueprint-mcp-windows.exe

Building

Package (for PyPI)

bash scripts/build-package.sh
# Output: dist/blueprint_mcp-<version>.tar.gz + .whl

Self-contained executable (current platform)

uv sync --dev
uv run python build_executables.py
# Output: dist/blueprint-mcp-{linux|macos|windows}

All platforms via CI

Push a tag v* to trigger the GitLab CI pipeline, which builds executables for all 3 platforms and publishes to PyPI.

Development

See CONTRIBUTING.md for full developer setup, VS Code integration, and the release workflow.

uv sync --dev
uv run pytest

License

This software is proprietary and confidential. Copyright (c) 2025 Sitemule. All rights reserved.

A valid commercial license from Sitemule is required for any use. See the LICENSE file for details.

Metadata

Release files for blueprint-mcp 1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for blueprint-mcp 1.1.1
File Size Uploaded Provenance Actions
blueprint_mcp-1.1.1.tar.gz 23.0 kB Without provenance Details for blueprint_mcp-1.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for blueprint-mcp 1.1.1
File Interpreter ABI Platform Actions
blueprint_mcp-1.1.1-py3-none-any.whl Python 3 none any Details for blueprint_mcp-1.1.1-py3-none-any.whl

Total release size: 44.5 kB

Release files / blueprint_mcp-1.1.1.tar.gz

Download URL blueprint_mcp-1.1.1.tar.gz
Size 23.0 kB
Tags Source
SHA-256 checksum
How to use checksums
93d4279dfc9db389cfea3c471cb189c3b84946f703fd477d6a3e33e2b381bbdf
BLAKE2b-256 checksum
How to use checksums
9e92649257be3024a5f57b5bca4933dcd6fa3ee742b168921ce1544ba273be81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / blueprint_mcp-1.1.1-py3-none-any.whl

Download URL blueprint_mcp-1.1.1-py3-none-any.whl
Size 21.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c557919a08df3c2ac1edb6d7b82862b8db038794dec257ce8d51abea7178d5ad
BLAKE2b-256 checksum
How to use checksums
81aaee4d57e32ddf7c3ba9a68956136cc0aaf3005eeccd10dc906077a57650ca
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.11.8 {"installer":{"name":"uv","version":"0.11.8","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for blueprint-mcp 1.1.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.1.1 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page