Queue CallBack

com.queuecallbackPublished by queuecallback.comOfficial publisherv1.0.0Updated Nov 6, 2026

Reporting, callback operations, queue settings and Custom IVR flows for RingCentral call queues.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server for RingCentral call queues: reporting, callback operations, queue settings and Custom IVR flows.

What you can do
  • Inspect reporting on RingCentral call queues.
  • Work with callback operations for queued callers.
  • Adjust queue settings.
  • Manage Custom IVR flows.
When to use it
Useful when you administer RingCentral call queues and want an assistant to look up queue reporting, handle callback operations, or adjust queue settings and IVR flows without switching tools.
Requirements
Remote streamable HTTP endpoint at mcp.queuecallback.com. OAuth is required; an optional Queue CallBack API key is sent as an Authorization Bearer header. Claude and ChatGPT can instead sign in with a Queue CallBack account, which is read-only; other clients and any change need the API key.
Before you install
The API key is a secret passed in the Authorization header. Account sign-in through Claude or ChatGPT is read-only, so changes require the key. Queue settings, callback operations and IVR flows can alter how live callers are handled, so review changes before applying them.

Installation

In SourceWeft

  1. Open Queue CallBack in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.queuecallback%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "queue-callback": {
      "type": "http",
      "url": "https://mcp.queuecallback.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 6, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.