Skip to main content
The MCP server gives an assistant the tools. Skills and apps give it the operating knowledge — which tool to use, in what order, and when to stop and ask. All of them sit on top of @ringee-io/agent, which holds the shared tool catalog, flows, prompts and safety rules. No business logic is duplicated: the Ringee backend stays the single source of truth.

​
Claude Code plugin

The plugin bundles the Ringee MCP server and the /ringee skill commands in one install.
On enable, Claude Code asks for your Ringee MCP URL and stores it in the keychain. Get it from the dashboard, or from GET /api/mcp/connection-info — see Connect a client. Update later with /plugin marketplace update.

​
Skill commands

Each skill enforces the confirmation rules in Safety — credit spend and destructive actions always stop for a human yes.

​
claude.ai

claude.ai does not use Claude Code plugins. It needs the two pieces separately.
1

Add the MCP as a connector

Settings → Connectors → Add custom connector, then paste your Ringee MCP URL. The server must be reachable from the public internet.
2

Upload the skills

Build the upload-ready zips from the repo:
Then Settings → Customize → Skills → Upload skill and upload each zip. Skills require code execution to be enabled.
3

Use them

Type / in any chat and pick a Ringee command, or just describe what you want.
On Team and Enterprise plans, upload once for everyone under Organization settings → Skills using the same zips.

​
Installing skills into a project

For Claude Code, copy the skills straight into a project’s .claude/skills:

​
ChatGPT app

The ChatGPT app is itself an MCP server (apps/chatgpt-app) that proxies the Ringee tools and renders them as visual cards — contact lists, call sessions, workspace switchers — instead of walls of JSON. Widgets are compiled into a bundle and inlined into each tool’s HTML resource, so the MCP server is the only thing you deploy.
1

Build the widgets

2

Run it locally

Test with npx @modelcontextprotocol/inspector against http://localhost:4250/mcp, or expose it with ngrok http 4250 and add it as a connector in ChatGPT developer mode.
3

Deploy behind HTTPS

The connector URL is https://<host>/mcp.
4

Add OAuth

ChatGPT requires OAuth 2.1 for connectors that touch user data. Point it at Clerk (or any OAuth 2.1 server with PKCE and published JWKS):
If you only need the Ringee tools in ChatGPT without custom widgets, connect the backend’s authenticated endpoint directly: https://api.ringee.io/api/mcp/chatgpt/sse. See Connect a client.

​
Domain verification

OpenAI’s developer portal verifies you control the MCP hostname by fetching a fixed token:
The backend serves it verbatim as text/plain from OPENAI_APPS_CHALLENGE_TOKEN. Each verified origin gets its own token — the backend and a separately deployed ChatGPT server cannot share one.

​
Next steps

ringee CLI

The same capabilities from a terminal

Agent layer

Build your own agent on @ringee-io/agent