Rcloud MCP Server

Created By
rongclouda year ago
rongcloud-server-mcp-python is an MCP server built on the FastMCP framework, integrating RongCloud instant messaging services. It supports user management, message sending, group operations, and more.
Overview

What is Rcloud MCP Server?

Rcloud MCP Server is an MCP server built on the FastMCP framework, integrating RongCloud instant messaging services. It provides functionalities for user management, message sending, group operations, and more.

How to use Rcloud MCP Server?

To use Rcloud MCP Server, clone the repository, set up the environment variables with your RongCloud credentials, and run the server using the provided commands.

Key features of Rcloud MCP Server?

  • User registration and management via RongCloud.
  • Sending private and group messages.
  • Retrieving user information and historical messages.
  • Group chat management including creation, dismissal, and member management.

Use cases of Rcloud MCP Server?

  1. Building chat applications with user management features.
  2. Implementing real-time messaging systems.
  3. Creating group chat functionalities for social or business applications.

FAQ from Rcloud MCP Server?

  • What programming language is used?

Rcloud MCP Server is built using Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I contribute to the project?

You can fork the repository, create a feature branch, and submit a pull request after making your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rongcloud
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.

23 minutes ago