# MCP server

> Connect Claude, ChatGPT, and other AI agents to your brand's live Rendezvu data. Setup for each client, the tool reference, the security model, and troubleshooting.

- Audience: Brands
- Page type: reference
- Updated: 2026-10-09
- Canonical URL: https://www.rendezvu.co/docs/brands/integrations/mcp

Server URL: `https://api.rendezvu.co/mcp`

## 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.

_Diagram: your AI client on the left, the Rendezvu MCP server in the middle, and your brand data (attributed sales, host performance, campaigns) on the right. One connector, one door onto your own data._

## 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.

- **Ask in plain language**: No dashboard to learn and no export to reconcile. Ask who your top five hosts were last quarter and you get the answer, with the numbers behind it.
- **Answers from live data**: Every response is a query that runs the moment you ask. It is your current Rendezvu data, not a report someone pulled last week.
- **Your brand, and only your brand**: Scope comes from your admin access and is recomputed on every request. There is no question you can phrase that returns another brand's sales, clicks, campaigns, or gifts. The discovery tools read only what hosts publish in their public gear lists.
- **Read only by construction**: The connector carries read tools only. Nothing an assistant does through it can change a campaign, a host, or a payment.
- **Sits inside the work**: The numbers arrive in the same conversation where you are drafting the board update, briefing an athlete, or writing the monthly recap.
- **Nothing to install**: It is a hosted server, so there is no package, no local process, and no API key to pass around. You sign in with your Rendezvu account.

## 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, [book a demo](https://calendly.com/hunter-rendezvu/demo) and we will get you set up.

**Claude**

Claude web, desktop, and mobile share one Connectors setting.

1. Open **Settings**, then **Connectors**.
2. Click **Add custom connector**.
3. Paste `https://api.rendezvu.co/mcp` as the server URL and save.
4. Click **Connect**. A Rendezvu sign-in page opens. Use your email and password, or continue with Google.
5. Approve the connection. The Rendezvu tools now show up in your chats.

> **Team and Enterprise plans**
>
> An organization Owner has to add the connector for the whole org before members can turn it on.

**Claude Code**

Add the server, then sign in when prompted.

```bash
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 config**

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.

```json
"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**

1. Open **Settings**, then **Apps**, then **Advanced settings**, and turn on **Developer mode**.
2. Add a connector by URL, using `https://api.rendezvu.co/mcp`.
3. Sign in with your Rendezvu account.

> **Business and Enterprise workspaces**
>
> An admin has to allow the connector under Settings, then Permissions and Roles, then Connected Data. Developer mode is available on Plus, Pro, Business, Enterprise, and Edu.

## Verify the connection

Open a new chat and ask for something only your Rendezvu data can answer:

> "What does my Rendezvu brand summary look like?"

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 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.

| Tool | What it returns |
| --- | --- |
| `get_brand_summary` | A one-call overview of your brand: how many hosts recommend you, how many of your products are in active lists, your top recommenders, recent activity, and the endorsement notes hosts have written about your gear. |
| `sales_attribution` | Every attributed sale and commission across Shopify, AvantLink, Impact, AWIN, Partnerize, and CJ, with the host who drove it, the revenue, and the commission. Filter by host, network, status, or date range. |
| `host_performance` | One host’s full report: profile views, list views, product clicks, buy-now clicks, attributed sales, revenue, and commission. Ask for all hosts to get a ranked leaderboard instead. |
| `click_funnel` | The weekly conversion funnel from profile view to list view to product click to buy-now click to sale, with the conversion rate at every stage. |
| `opportunity_pipeline` | Search and list your campaigns: status breakdown, host counts, payment states, deadlines, and anything stuck. This is how a plain-language reference to a campaign becomes something the next tool can look up. |
| `get_opportunity` | A deep dive on one campaign, found by partial name, id, or assignment code: the exact title, the brief as plain text, deliverables, hosts and their codes, payment terms, and per-host invite states. |
| `list_brand_gifts` | Your Gifting page, read directly: every product gift you have sent a host, where it sits (pending, accepted, shipped, complete), the date of each step, tracking, the campaign it came from, and the host’s feedback. Every accepted gift includes the recipient’s name and the full shipping address they submitted, so you can label and track the box. Phone numbers and emails are never returned. Needs a plan that includes gifting. |
| `gear_recommendation` | The products of yours best suited to a given ask, with the recommending host’s expertise, notes, and pricing. Filter by sport, category, price, or host. |
| `find_brand_recommenders` | The hosts who currently carry a brand’s products in their public gear lists, with how many products each carries, sample products, their endorsement in their own words, and whether they are already on your roster. Leave the brand out to search your own; name another brand to see who recommends it. Needs a plan that includes Discover. |
| `get_host_gear` | One host’s full public gear presence: every active gear list, every product in it, and every endorsement they wrote, plus their brand mix and whether they are on your roster. Needs a plan that includes Discover. |
| `gear_list_insights` | What hosts recommend, rolled up across Rendezvu’s public gear lists: adoption per product, a cross-brand adoption comparison, or the lists themselves. Built only from public gear lists, never from another brand’s sales. Needs a plan that includes Discover. |
| `get_skills` | Your brand’s saved skills: brand identity, the hosts you want, regions, focus sports, partnership style, voice and tone, and current goals. Standing context, so you do not have to re-explain your brand every session. |
| `rendezvu_docs` | The public Rendezvu documentation at rendezvu.co/docs, searchable: how host profiles, gear lists, sharing and direct links, host payouts, brand partnerships, opportunities, and this connector work. It answers how the product works, not what your numbers say, so an assistant can look a feature up instead of guessing at it. |
| `rendezvu_brand_assets` | The official Rendezvu logos in every variation, as public SVG and PNG links with usage rules, so a co-branded deck, email or page uses the real files. |
| `think` | A scratchpad the assistant uses to plan which tool to reach for. It touches no data and takes no action. |

## Security and scope

- **Read only, enforced twice**: Brand 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 request**: Your 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 account**: Revoke 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 secret**: Signing in issues an access token that lives one hour and refreshes itself in the background. Your AI client holds it. Nobody pastes a key into a config file.
- **Rate limited per brand**: Thirty requests per minute, counted per brand. A burst from one teammate cannot exhaust another brand's quota.

## Data and privacy

What the connector reads, what Rendezvu records, and what reaches your AI provider:

- **What it reads.** Only data for the brands you administer: attributed sales and commissions, click and conversion analytics, host performance, your campaigns, your gifting records (including the shipping address a host submitted, if your plan includes gifting), and your saved brand skills. It also reads public Rendezvu information, such as the gear lists and endorsement notes hosts publish, the public docs, and Rendezvu's logos.
- **What it never returns.** Passwords, payment card details, host email addresses or phone numbers, and any other brand's sales, clicks, campaigns, or gifts.
- **What Rendezvu records.** For each request: the time, your account, the brands in scope, the AI client's name, the tool used, whether it succeeded, and how long it took. Not your conversation, and not the contents or results of the request.
- **What your AI provider receives.** The results of the requests your assistant makes. Your provider processes them under its own terms and privacy policy, including its settings for retention and model training.

The full detail is in the [AI assistant connectors section of our Privacy Policy](https://rendezvu.co/privacy-policy#ai-connectors), and the terms of use are in [Section 1.12 of our Terms](https://rendezvu.co/terms-and-conditions#ai-connectors).

## Disconnect and revoke access

- **Disconnect one client.** Remove or disconnect the Rendezvu connector in your AI assistant's settings (in Claude, **Settings**, then **Connectors**; in ChatGPT, **Settings**, then **Apps**).
- **Remove a teammate.** Remove their brand admin access in Rendezvu. Their connector stops returning data on its next request, even if a token has not expired yet.
- **Revoke everything.** Email [support@rendezvu.co](mailto:support@rendezvu.co) and we will revoke every connector token on your account.

## Troubleshooting

**Sign-in sends me back with an access_denied error**

The connector is for brand admins. Your Rendezvu account needs at least one active brand admin assignment, and host accounts are not eligible. If you think you should have access, ask your team's Rendezvu admin to add you, or email support@rendezvu.co.

**The Rendezvu tools do not appear in my chat**

Tools are listed when the session connects, so a conversation that started before you added the connector will not see them. Start a new chat, or restart the client, then confirm the connector is enabled for that conversation.

**The assistant answers without querying anything**

Models will sometimes answer from what is already in the conversation. Name the source in your prompt, for example "use the Rendezvu connector to pull last month's sales", and ask which tool it called. If it cannot name one, it did not query your data.

**The numbers do not match my Rendezvu console**

Check the window before you check the math. Most tools default to the last 30 days and the funnel defaults to the last eight weeks, so an unqualified question rarely covers the period you had in mind. State the range you want.

**Requests start failing after a burst of questions**

That is the rate limit, which is 30 requests per minute per brand. Wait a minute and carry on. A single long question can spend several requests, because the assistant may call more than one tool to answer it.

Still stuck? Email [support@rendezvu.co](mailto:support@rendezvu.co) and tell us which client you are using and what the assistant said.

## Related

- [Integrations](https://www.rendezvu.co/docs/brands/integrations.md): Connect your store so orders attribute to the host who caused them. Shopify, Squarespace and WooCommerce, plus the AI connectors and the public API.
- [Ask Rendezvu](https://www.rendezvu.co/docs/brands/ask-rendezvu.md): The assistant in your console, wired to your live data. What it can read, why every change waits for your approval, and how to steer it.
- [Analytics](https://www.rendezvu.co/docs/brands/analytics.md): What the console counts, what each number means, and why orders and revenue are the measures to trust rather than raw click counts.

---

Source: https://www.rendezvu.co/docs/brands/integrations/mcp (Rendezvu docs, Markdown view). Every page: https://www.rendezvu.co/llms.txt