RTC MCP Server

Created By
gnuhpca year ago
A Model Context Protocol (MCP) server implementation for managing Alibaba Cloud Realtime Computing Flink resources
Overview

What is RTC MCP Server?

RTC MCP Server is a Model Context Protocol (MCP) server implementation designed for managing Alibaba Cloud Realtime Computing Flink resources, providing a standardized interface for AI models to interact with Flink services.

How to use RTC MCP Server?

To use the RTC MCP Server, configure your MCP settings file with the server details and your Alibaba Cloud credentials, then run the server using Java.

Key features of RTC MCP Server?

  • Create and manage Flink clusters
  • Manage Flink SQL jobs
  • Deploy and control Flink applications
  • Monitor job status and metrics
  • Manage savepoints and deployments
  • Workspace and namespace management

Use cases of RTC MCP Server?

  1. Managing Flink clusters for real-time data processing.
  2. Deploying and monitoring Flink applications in cloud environments.
  3. Facilitating AI model interactions with Flink services.

FAQ from RTC MCP Server?

  • What are the prerequisites to use RTC MCP Server?

You need JDK 17 or higher, Maven 3.6 or higher, and an Alibaba Cloud account with RTC access.

  • How do I deploy a Flink job?

Use the start_job command after creating a deployment.

  • Is there support for multiple transport modes?

Yes, the server supports both webflux and stdio modes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gnuhpc
Star
0
Language
-
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