Boomi MCP Server

Secure MCP server for Boomi Platform API integration with Claude Code

A production-ready Model Context Protocol (MCP) server that enables Claude Code and other MCP clients to interact with Boomi Platform APIs using OAuth 2.0 authentication and secure credential storage.

🌐 Live Service: https://boomi.renera.ai

---

Features

- 🔐 Google OAuth 2.0 - Secure authentication with consent screen
- 🔒 GCP Secret Manager - Encrypted per-user credential storage
- 👤 Multi-Profile Support - Store up to 10 Boomi account profiles per user
- 🌐 Web UI - Browser-based credential management
- ✅ Credential Validation - Test credentials before saving
- 🚀 Auto-Deploy - GitHub push → Cloud Build (pinned KB release) → Cloud Run
- 📦 MCP Tools - 29 tools spanning trading partners, processes, components, runtimes, deployments, schedules, account management, and more
- 📚 Boomi Docs KB - Optional retrieval-augmented search_boomi_docs / read_boomi_doc_page tools backed by a pinned knowledge-base release
- ☁️ Cloud Native - Running on Google Cloud Run

---

Quick Start

For Users

1. Visit the Web UI: https://boomi.renera.ai
2. Login with Google - OAuth authentication
3. Add Boomi Credentials:
- Email: Your Boomi account email
- API Token: Your Boomi API token
- Account ID: Your Boomi account ID
- Profile Name: A name for this credential set (e.g., "production", "sandbox")

4. Connect Claude Code:

claude mcp add --transport http boomi https://boomi.renera.ai/mcp

5. Authorize - Browser opens for OAuth consent, click "Approve"

6. Use MCP Tools:

Show me my Boomi account information from the production profile

---

Architecture

┌──────────────┐
│    User      │
│  (Browser)   │
└──────┬───────┘
       │ 1. Visit https://boomi.renera.ai
       │ 2. Google OAuth Login
       ▼
┌──────────────────────────────────────┐
│      Boomi MCP Server (Cloud Run)    │
│  ┌────────────┐    ┌──────────────┐ │
│  │  Web UI    │    │  MCP Server  │ │
│  │ (FastAPI)  │    │  (FastMCP)   │ │
│  └────────────┘    └──────────────┘ │
└───────┬──────────────────┬───────────┘
        │                  │
        │ Store            │ Retrieve
        │ Credentials      │ Credentials
        ▼                  ▼
┌──────────────────────────────────────┐
│      GCP Secret Manager              │
│  boomi-mcp-{user-id}-{profile-name}  │
└──────────────────────────────────────┘
                    │
                    │ API Calls
                    ▼
             ┌──────────────┐
             │  Boomi API   │
             └──────────────┘

---

Available MCP Tools

The server exposes 29 tools. All tools require an authenticated session and a
valid profile parameter pointing at a stored Boomi credential set.

Account & profile management

- list_boomi_profiles() — list saved credential profiles for the current user. - boomi_account_info(profile) — fetch account details for the named profile. - set_boomi_credentials(...) / delete_boomi_profile(...) — credential CRUD. - manage_account(...), manage_account_groups(...) — Boomi account admin.

Build, deploy, and operate integrations

- manage_process (read-only process list/get), manage_component, analyze_component, query_components, build_integration, get_schema_template - manage_environments, manage_runtimes, manage_deployment, execute_process, troubleshoot_execution, manage_schedules, manage_listeners, manage_integration_packs - manage_trading_partner, manage_connector, manage_shared_resources, manage_folders, monitor_platform

Escape hatches

- invoke_boomi_api(...) — call any Boomi REST endpoint when no dedicated tool exists. - list_capabilities() — discoverability helper that summarizes all registered tools.

Boomi Docs Knowledge Base (optional)

Registered only when the server starts with BOOMI_DOCS_ENABLED=true and a
populated KB at BOOMI_DOCS_DB_PATH:

- search_boomi_docs(query, ...) — semantic search across the indexed
Boomi documentation corpus.
- read_boomi_doc_page(page_key) — fetch the full markdown for a specific
documentation page.
- Resource kb://boomi-docs/corpus — corpus manifest (release tag, page
count, generated-at metadata).

The KB corpus is built and released by
RenEra-ai/knowledge-base-builder
and embedded into the image at build time via
deploy/kb-release.env. See
KB Release Promotion below.

Cold-start behavior (operators). The heavy KB build (Chroma + embedding
model load) is deferred off the import path so the server binds its HTTP port
immediately — the docs tools are registered before the KB is ready. On a
scale-to-zero cold start the first call(s) may return a bounded
error: warming_up (still loading — clients should wait retry_after_seconds
and retry) or error: kb_unavailable (temporary build failure — self-heals on a
later call after a cooldown). A docs call no longer hangs while the corpus loads.
Tuning env vars: BOOMI_DOCS_WARMUP_WAIT_SECONDS (default 5 — max seconds a call
blocks waiting for warmup), BOOMI_DOCS_WARMUP_EAGER (default true — kick the
build on the first authenticated /mcp request; pinned false in
cloudbuild.yaml since 2026-06-01 so the heavy model load defers to the first
docs call and never contends with non-docs tools on a cold 1-vCPU instance),
BOOMI_DOCS_WARMUP_RETRY_COOLDOWN
(default 30 — seconds before a failed build re-attempts).

Boomi Operational Gotchas KB (optional)

Registered only when the server starts with BOOMI_GOTCHAS_ENABLED=true. This is
a separate surface from the docs KB (operational field knowledge vs official
documentation) and is gated by its own independent flag:

- search_boomi_gotchas(query, top_k=5, issue_ids=None) — search a curated
catalog of known Boomi silent-failure modes and field traps. Pass issue_ids
for a deterministic exact lookup by gotcha id (it takes precedence over
query). Empty/no-match behavior is explicit and never fabricates entries.
- Resource kb://boomi-operational-gotchas/catalog — the full catalog with each
entry's symptom, detection/frequency taxonomy, provenance, and
verification_status.

Unlike the docs KB, this catalog is stdlib-only: an in-repo curated dataset
with deterministic lexical ranking, no requirements-kb.txt / chromadb /
embedding dependency. Entries are curated summaries (OfficialBoomi BSD-2-Clause
material + local issue/architect-course triage), not verbatim copies, and carry a
verification_status (live_verified / docs_corroborated /
companion_unverified / course_unverified / disputed) so agents can weigh how
well-corroborated each claim is.

---

Deployment

Current Production Deployment

- Hosting: Google Cloud Run (us-central1)
- URL: https://boomi.renera.ai
- CI/CD: Automated via GitHub
- Region: us-central1
- Authentication: Google OAuth 2.0

CI/CD Pipeline

Automatic deployment on push to main branch:

GitHub Push → Cloud Build (cloudbuild.yaml) → Docker Build (KB pin) → Artifact Registry → Cloud Run

The pipeline is source-controlled in cloudbuild.yaml and
embeds a pinned Boomi Docs knowledge-base release into the image. The KB tag
lives in deploy/kb-release.env so every corpus
version change is a visible repo edit — builds must never use a floating
latest KB release.

KB Release Promotion

1. In RenEra-ai/knowledge-base-builder, cut a manual workflow_dispatch
release (for example kb-13). The release must publish
boomi_knowledge_db.tar.gz as an asset.
2. In this repo, bump the single line in deploy/kb-release.env:

   KB_RELEASE_TAG=kb-13

   

3. Open a PR with that change and merge to main.
4. The Cloud Build trigger reads cloudbuild.yaml, runs a curl -fI
preflight against the GitHub release asset, then builds the image with
--build-arg KB_RELEASE_TAG=$KB_RELEASE_TAG. A missing or empty pin
fails the build before any Docker work happens.
5. Cloud Run is updated with BOOMI_DOCS_ENABLED=true,
BOOMI_DOCS_DB_PATH=/app/kb/boomi_knowledge_db, and
BOOMI_DOCS_RELEASE_TAG=<tag>, which causes the server to register the
search_boomi_docs and read_boomi_doc_page tools plus the
kb://boomi-docs/corpus resource at startup.

Cloud Build Trigger Migration

The existing trigger 8623a6fa-3295-430a-b018-7c728ba941e8 was created from
an inline auto-generated config that did not pass KB_RELEASE_TAG and did
not set the KB runtime env vars. Point it at the source-controlled config
once:

gcloud builds triggers update github 8623a6fa-3295-430a-b018-7c728ba941e8 \
  --project=boomimcp \
  --region=global \
  --build-config=cloudbuild.yaml

After migration, every push to main runs the steps in cloudbuild.yaml
and a git log -- cloudbuild.yaml deploy/kb-release.env shows exactly which
KB version is live.

Manual Deployment

If you need to deploy manually (skips the GitHub trigger):

```bash