Rindee

ai.rindeePublished by rindee.aiOfficial publisherv1.0.0Updated Nov 7, 2026

AI phone agents for service businesses: calls, appointments, contacts, agents and Knowledge.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server for Rindee's AI phone agents for service businesses, covering calls, appointments, contacts, agents and Knowledge.

What you can do
  • Work with AI phone agents for service businesses
  • Handle calls and call-related activity
  • Manage appointments
  • Manage contacts
  • Manage agents and Knowledge content
When to use it
Worth adding when a service business runs Rindee AI phone agents and wants an assistant to work with its calls, appointments, contacts, agents or Knowledge alongside other tools. The listing gives no tool details, so confirm the exact capabilities in Rindee's documentation before relying on it.
Requirements
A remote MCP endpoint at api.rindee.ai over streamable HTTP. OAuth authentication is required, so a Rindee account with access to the relevant workspace is needed. No environment variables or headers are declared.
Before you install
The server handles business phone calls, appointments and contacts, so an assistant may read or change customer data; check what write actions are exposed before connecting. Access is granted through OAuth to a Rindee account, so review the scopes requested. No tool list is published, so the exact operations are unverified.

Installation

In SourceWeft

  1. Open Rindee 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/ai.rindee%2Frindee/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": {
    "rindee": {
      "type": "http",
      "url": "https://api.rindee.ai/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 7, 2026

Score

83% 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
  • 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.