The Rendezvu MCP server connects Claude, ChatGPT, and other AI agents to your brand’s live Rendezvu data, so you can ask it anything.
Overview
What is an MCP server?
An MCP (Model Context Protocol) server is an authenticated API that an AI assistant can use to read data from a specific platform. Adding one is called adding a connector.
The Rendezvu MCP server gives an assistant a small set of read-only tools that query your own brand data: attributed sales, host performance, the conversion funnel, your campaign pipeline, the notes athletes have written about your gear. When you ask a question, the assistant picks a tool, runs it against live Rendezvu data, and answers from what came back.
It is a hosted server, so there is nothing to install. You add one URL to your AI client, sign in with the Rendezvu account you already have, and the connector is live.
One connector, and it is the only door onto your data. Your client asks, the server runs a scoped read, and the answer comes back.
Why connect it
Your Rendezvu console already shows you everything. The connector is about the questions that a dashboard makes slow: the ones that cross campaigns and hosts and months, and the ones you did not know you wanted until you were already writing something else.
What you can ask
Every one of these maps onto a tool in the reference below, so none of them are hypothetical.
- “How much revenue did our ambassadors drive in the last 30 days?”
- “Who are our top five hosts this quarter, ranked by revenue?”
- “What is our product-click to sale conversion rate over the last eight weeks?”
- “Which campaigns are stuck in DRAFT, and which deadlines are coming up?”
- “Which athletes have written notes about our products?”
- “Pull the brief, deliverables, and host codes for the spring trail campaign.”
- “Draft a monthly performance recap for our leadership team from last month.”
Getting started
Before you start
You need a Rendezvu brand admin account. Sign-in checks that your account has at least one active brand assignment, and anything else, including host accounts, is turned away. If your brand is not on Rendezvu yet, and we will get you set up.
Claude web, desktop, and mobile
- Open Settings, then Connectors.
- Click Add custom connector.
- Paste
https://api.rendezvu.co/mcpas the server URL and save. - Click Connect. A Rendezvu sign-in page opens. Use your email and password, or continue with Google.
- Approve the connection. The Rendezvu tools now show up in your chats.
Claude Code
Add the server, then sign in when prompted.
claude mcp add --transport http rendezvu https://api.rendezvu.co/mcp
Run /mcp inside Claude Code, pick rendezvu, and complete the sign-in in your browser. The token is stored by Claude Code, so this is a one-time step.
Claude Desktop, edited by hand
If you would rather edit the config file than use the Connectors UI, go to Settings, then Developer, then Edit Config, and add the block below.
"mcpServers": {
"rendezvu": {
"command": "npx",
"args": ["mcp-remote", "https://api.rendezvu.co/mcp"]
}
}Restart Claude Desktop. The first request opens the Rendezvu sign-in page in your browser.
ChatGPT
- Open Settings, then Apps, then Advanced settings, and turn on Developer mode.
- Add a connector by URL, using
https://api.rendezvu.co/mcp. - Sign in with your Rendezvu account.
Verify the connection
Open a new chat and ask for something only your Rendezvu data can answer:
The assistant should ask permission to use the Rendezvu connector, then come back with your recommender count, your product count, and your top recommenders. If it answers without ever asking permission, it did not query anything. Tell it to use the Rendezvu connector and ask again.
Tool reference
These are the nine tools a brand connector gets. All of them are read-only. Tools that write, that read across brands, or that run raw SQL are internal to Rendezvu and are never listed to a brand connector, let alone callable by one.
Security and scope
- Read only, enforced twiceBrand connectors are given read tools only, and the database role behind the connector refuses writes regardless. Creating and editing campaigns stays inside Rendezvu.
- Scope is recomputed per requestYour scope is derived from your active brand admin assignments every single time you ask something. Gain access to another brand and it is included on the next query. Lose it and it is gone from the same moment.
- Access follows the accountRevoke a teammate’s Rendezvu admin access and their connector stops returning data on its next request. There is no separate credential to hunt down and rotate.
- Short-lived tokens, no shared secretSigning in issues an access token that lives one hour and refreshes itself in the background. Your Claude client holds it. Nobody pastes a key into a config file.
- Rate limited per brandThirty requests per minute, counted per brand. A burst from one teammate cannot exhaust another brand’s quota.