Seatunnel

Created By
ocean-zhca year ago
Overview

what is SeaTunnel MCP?

SeaTunnel MCP is a Model Context Protocol server designed for interacting with SeaTunnel through LLM interfaces like Claude.

how to use SeaTunnel MCP?

To use SeaTunnel MCP, clone the repository, set up a virtual environment, install the required packages, and configure the environment variables for the SeaTunnel API. You can then run the server and manage jobs through the provided tools.

key features of SeaTunnel MCP?

  • 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

use cases of SeaTunnel MCP?

  1. Submitting and managing data integration jobs.
  2. Monitoring the status of SeaTunnel jobs in real-time.
  3. Configuring connections to different SeaTunnel instances dynamically.

FAQ from SeaTunnel MCP?

  • What is required to run SeaTunnel MCP?

You need Python ≥ 3.9, a running SeaTunnel instance, and Node.js for testing.

  • How do I manage jobs with SeaTunnel MCP?

You can submit, stop, and monitor jobs using the provided commands.

  • Can I change the connection settings at runtime?

Yes! The server allows you to view and update connection settings dynamically.

Server Config

{
  "mcpServers": {
    "seatunnel": {
      "command": "python",
      "args": [
        "-m",
        "src.seatunnel_mcp"
      ],
      "cwd": "Project root directory",
      "env": {
        "SEATUNNEL_API_URL": "http://localhost:8090"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ocean-zhc
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

an hour ago
Gpt Scrambler

2 days ago