Boomi MCP Server

Created By
Glebuara year ago
An MCP server for interaction with the Boomi API.
Overview

What is Boomi MCP Server?

Boomi MCP Server is a Model Context Protocol (MCP) server designed for seamless interaction with the Boomi API, exposing various SDK operations as MCP tools.

How to use Boomi MCP Server?

To use the Boomi MCP Server, you can run it via Docker or build it from source. Set your Boomi API credentials using environment variables or a .env file, and then start the server.

Key features of Boomi MCP Server?

  • Exposes 85+ tools for the complete Boomi integration lifecycle.
  • Supports core workflow operations like discovery, development, packaging, deployment, execution, monitoring, and debugging.
  • Provides advanced features such as queue management, audit logs, and document rerun capabilities.

Use cases of Boomi MCP Server?

  1. Automating Boomi integration tasks.
  2. Monitoring and managing Boomi processes programmatically.
  3. Integrating with other applications using the Boomi API.

FAQ from Boomi MCP Server?

  • What are the requirements to run Boomi MCP Server?
    You need Python 3.10+ and access credentials for the Boomi API.

  • Can I run it without Docker?
    Yes, you can build and run it from source if you prefer not to use Docker.

  • Is there a Python client available?
    Yes, a Python client is included for programmatic access to the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Glebuar
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago