1. Conduid
  2. Data
  3. Flink MCP
MCP server · Data

Flink MCP

by · github.com/Cledar/flink-mcp

MCP server for Apache Flink SQL Gateway

Unclaimed last commit 12 months ago data
InstallView source
43Fair

Scored 3 months ago · breakdown

About Flink MCP

Flink MCP is an MCP server published by Cledar in the Data category: mCP server for Apache Flink SQL Gateway. It has been installed 0 times through Conduid.

The repository has 8 stars and 3 forks, with the last commit 12 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx flink-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Flink MCP

Powered by Claude · Grounded in docs

I know everything about Flink MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

flink-mcp — Flink MCP Server

This project provides an MCP server that connects to Apache Flink SQL Gateway.

Prerequisites

  • A running Apache Flink cluster and SQL Gateway

    • Start cluster: ./bin/start-cluster.sh
    • Start gateway: ./bin/sql-gateway.sh start -Dsql-gateway.endpoint.rest.address=localhost
    • Verify: curl http://localhost:8083/v3/info

  • Configure environment:

    • Set SQL_GATEWAY_API_BASE_URL (default http://localhost:8083). You can use a .env file at repo root.

Run

Install and run via the console script:

pip install -e .
flink-mcp

MCP clients should launch the server over stdio with command: flink-mcp.

Ensure SQL_GATEWAY_API_BASE_URL is set in your environment or .env.

Tools (v0.2.5)

  • flink_info (resource): returns cluster info from /v3/info.
  • open_new_session(properties?: dict) -> { sessionHandle, ... }.
  • get_config(sessionHandle: str): returns session configuration.
  • configure_session(sessionHandle: str, statement: str): apply session-scoped DDL/config (CREATE/USE/SET/RESET/LOAD/UNLOAD/ADD JAR).
  • run_query_collect_and_stop(sessionHandle: str, query: str, max_rows: int=5, max_seconds: float=15.0): execute, fetch up to N rows within T seconds, then STOP the job if a jobID is present; closes the operation.
  • run_query_stream_start(sessionHandle: str, query: str): execute a streaming query and return { jobID, operationHandle }; the job is left running.
  • fetch_result_page(sessionHandle: str, operationHandle: str, token: int): fetch a single page; returns { page, nextToken, isEnd }.
  • cancel_job(sessionHandle: str, jobId: str): issue STOP JOB '<jobId>', wait until DESCRIBE JOB status is not RUNNING; returns { jobID, status, jobGone, jobStatus }.

Notes

  • Tools are stateless; clients manage and pass session/operation handles explicitly.

  • run_query_stream_start returns both jobID and operationHandle; use fetch_result_page to stream results.

  • cancel_job issues STOP and waits using DESCRIBE JOB; close_operation is invoked internally where appropriate.

  • Endpoints target SQL Gateway v3-style paths.

README mirrored from the source repository 3 months ago. The original is authoritative.

Questions

About Flink MCP

How do I install Flink MCP?

Run npx flink-mcp, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Flink MCP safe to use with an AI agent?

Its trust score is 43 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Flink MCP still maintained?

The last commit was 12 months ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.