Ringnity MCP
Connect AI clients to Ringnity through a secure MCP layer. The MCP server exposes tools, while Ringnity API remains the source of truth for tenant isolation, scopes, plan contracts, quota, billing, and audit.
MCP Client
Claude, Cursor, OpenAI Agents, or custom AI client.
Ringnity MCP
Stateless adapter that exposes safe tools over Streamable HTTP.
Ringnity API
Source of truth for auth, tenant isolation, scopes, billing, quota, and business rules.
Quick Start
Use the Ringnity MCP endpoint from any MCP-compatible client that supports Streamable HTTP.
{
"mcpServers": {
"ringnity": {
"url": "https://mcp.ringnity.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_RINGNITY_TOKEN_OR_SERVER_API_KEY"
}
}
}
}Build a support app with a coding agent
The public ringnity_sdk_integration_guide tool gives Codex and other coding agents the current release, artifact, prerequisites, supported capabilities, implementation order, security boundary, explicit gaps, and acceptance checklist for the requested principal and capabilities.
Integrate Ringnity into my Flutter Android application.
The application must receive and reply to Visitor chat and internet calls.
Agents must also be able to chat and make audio/video calls to other Agents.
Use ringnity_sdk_integration_guide twice:
- platform: flutter
- principal: visitor
- capabilities: [support-chat, audio-call, video-call]
Then:
- platform: flutter
- principal: agent
- capabilities: [support-inbox, direct-chat, audio-call, video-call]
Inspect my project before editing, keep the Server API key outside the mobile
application, implement the required backend token boundary, and run the
release/profile acceptance checklist.STEP 1
Discover
Read the current release and official guide.
STEP 2
Validate
Resolve the tenant and check SDK readiness.
STEP 3
Implement
Coding agent edits the customer app; MCP remains read-only.
STEP 4
Accept
Build and test chat, calls, push, reconnect, and TURN/TLS.
MCP never installs packages, edits source code, sends messages, or joins media. The coding agent performs repository changes; the Ringnity Flutter SDK owns communication at runtime.
Build an authenticated chat or meeting product
Use the Member principal for authenticated application users. Ringnity owns tenant isolation, durable direct/group chat, receipts, P2P direct calls, managed group audio/video, realtime, reconnect, and transport policy. Your application owns sign-in, relationship rules, navigation, branding, call controls, and the participant layout.
Use ringnity_sdk_integration_guide with:
- platform: flutter
- principal: member
- capabilities: [identity, direct-chat, group-chat, audio-call, video-call, group-call, device-push, reconnect]
Build the UI from typed Ringnity state and media tracks. If the product also
requires screen sharing, recording, captions, or a waiting room, include those
capabilities so the guide reports them as explicit gaps instead of implying
that they already exist.Runtime actions stay in the SDK
MCP currently exposes authorized Team, group, active call-room, and capability snapshots only. It cannot create or join a room, invite or remove participants, transfer a host, end a call, select a media provider, or obtain a managed-media token. Write actions remain outside MCP so tokens, media credentials, and user mutations do not enter an AI transcript.
Public Tools
Health, pricing, and tenant resolution can be called without exposing tenant data.
Private Tools
Tenant contacts and conversations require scoped Server API, Agent SDK, or platform tokens.
No Direct DB
MCP calls Ringnity API. Prisma/database and business rules remain inside the core API.
Available Tools
| Tool | Auth | Purpose |
|---|---|---|
| ringnity_health | Public | Check Ringnity API reachability. |
| ringnity_public_pricing | Public | Read the pricing catalog used by ringnity.com. |
| ringnity_resolve_tenant | Public | Resolve a tenant slug into public workspace metadata. |
| ringnity_sdk_integration_guide | Public | Return a machine-readable SDK release, capability, security, implementation, and acceptance guide. |
| ringnity_server_tenant | Server API key | Read tenant context for a scoped Server API key. |
| ringnity_server_sdk_readiness | Server API key | Check SDK readiness for a tenant. |
| ringnity_list_push_provider_configs | server:push-provider:read | Inspect app-level FCM/APNs VoIP readiness without exposing credentials. |
| ringnity_list_contacts | server:contact:read | List tenant contacts. |
| ringnity_get_contact | server:contact:read | Read one tenant contact. |
| ringnity_agent_list_conversations | agent:conversations:read | List conversations visible to an agent. |
| ringnity_agent_get_conversation | agent:conversations:read | Read one conversation. |
| ringnity_agent_get_conversation_messages | agent:messages:read | Read conversation messages. |
| ringnity_agent_list_team_conversations | agent:conversations:read | List direct and group Team conversations. |
| ringnity_agent_list_groups | agent:conversations:read | List groups where the Agent is an active member. |
| ringnity_agent_list_call_rooms | agent:calls:read | Recover active or joinable call-room snapshots without joining media. |
| ringnity_agent_call_capabilities | agent:calls:read | Read plan entitlement and controlled-rollout readiness. |
| ringnity_plan_contracts | Platform/admin token | Read canonical plan feature and quota contracts. |
Call a Public Tool
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "ringnity_public_pricing",
"arguments": {
"currency": "USD",
"locale": "en"
}
}
}Call a Private Tool
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "ringnity_agent_list_call_rooms",
"arguments": {}
}
}Send the scoped Ringnity credential only in the MCP Authorization header shown in Quick Start. Credentials are not accepted in tool arguments.
Security Notes
Last updated: September 11, 2026
Turn Your Website Into a Real-Time Call Center
Let customers call your team directly from your website, no phone numbers and no apps required. Just add one <script>.
