SeaTunnel MCP Server

A Model Context Protocol (MCP) server for Apache Seatunnel. This provides access to your Apache Seatunnel RESTful API V2 instance and the surrounding

Local serverstdioPython

What is the SeaTunnel MCP server?

A Model Context Protocol (MCP) server for Apache Seatunnel. This provides access to your Apache Seatunnel RESTful API V2 instance and the surrounding ecosystem. Exposed over MCP by the seatunnel mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

A Model Context Protocol (MCP) server for interacting with SeaTunnel through LLM interfaces like Claude.

  • Job management (submit, stop, monitor)
  • System monitoring and information retrieval
  • REST API interaction with SeaTunnel services
  • Built-in logging and monitoring tools
  • Dynamic connection configuration
  • Comprehensive job information and statistics

Adding it to your client

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Configuration

You will need 2 environment variables: SEATUNNEL_API_URL, SEATUNNEL_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Python ≥ 3.12 * Running SeaTunnel instance * Node.js (for testing with MCP Inspector)

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the seatunnel mcp server does with a few real requests.

When to reach for it

This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by ocean-zhc; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

How to install the SeaTunnel MCP server

{
  "mcpServers": {
    "st-mcp-sse": {
      "url": "http://your-server:18080/sse"
    },
    "st-mcp-uv": {
      "command": "uv",
      "args": ["run", "seatunnel-mcp"],
      "env": {
        "SEATUNNEL_API_URL": "http://127.0.0.1:8080"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Python ≥ 3.12 * Running SeaTunnel instance * Node.js (for testing with MCP Inspector)
VariableDescriptionRequired
SEATUNNEL_API_URLEndpoint or connection string the server talks to.Yes
SEATUNNEL_API_KEYCredential the server authenticates with.Yes

Frequently asked questions

Python 3.12 or higher, a running SeaTunnel instance, and Node.js for testing with MCP Inspector.