> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/reo.dev-claude-connector.md).

# Reo.Dev Claude Connector

If you're new to the Reo Claude Connector - this starter kit has everything you need to get up and running!&#x20;

**What you’ll find here:**

* [How to connect Reo.Dev MCP to Claude ](https://docs.reo.dev/reo.dev-claude-connector#connect-reo.dev-mcp-to-claude)
* [Claude Skills ](https://docs.reo.dev/reo.dev-claude-connector#reo.dev-x-claude-skills)
* [Prompt Guide 101 ](https://docs.reo.dev/reo.dev-claude-connector#prompt-guide-101)

***

### Connect Reo.Dev MCP to Claude&#x20;

Follow the step-by-step guide to set up the Reo MCP connection on Claude:&#x20;

{% hint style="warning" %}
**Prerequisites:**

* Claude Desktop App
* Active [Reo.Dev](http://Reo.Dev) Account
* Data-out API & Product API enabled on Reo.Dev
* Log out of [Reo.Dev](http://Reo.Dev) Account
  {% endhint %}

**Step 1:** Log out of your Reo.Dev Account

<figure><img src="/files/XcsNezwOz4925oMa991l" alt=""><figcaption></figcaption></figure>

**Step 2:** Open the Claude desktop app > from the left navigation menu > select **Customize**

<figure><img src="/files/itAnrnUw1M9Snkhvbz81" alt=""><figcaption></figcaption></figure>

**Step 3:** A pop-up modal will open up. Under Customize > select **Connectors**

<figure><img src="/files/D8DuUk2Mi6cQJYSSG18L" alt=""><figcaption></figcaption></figure>

**Step 4:** From the top-right corner > click Add > Add custom connector

<figure><img src="/files/h0PIFubHP7wLyy1Bzhcp" alt=""><figcaption></figcaption></figure>

**Step 5:** Give it a name (example - Reo MCP) and enter the following remote URL <mark style="color:red;">`https://mcp.reo.dev/mcp`</mark> \
Then, click on Add.&#x20;

<figure><img src="/files/YFtpOOv7iqzfxakiDWan" alt=""><figcaption></figcaption></figure>

**Step 6:** Click on **Connect** > you will get redirected to the Reo.Dev web app. You will be required to log in to your Reo account to complete the setup.&#x20;

{% hint style="info" %}
**Note: To complete this step, ensure that you’re logged out of Reo.**&#x20;
{% endhint %}

<figure><img src="/files/lxwfciBHQefvqS0MPHIT" alt=""><figcaption></figcaption></figure>

**Step 7:** Once you log in to your Reo account, you will land back in Claude. You will see this success modal on the top-right corner.&#x20;

<figure><img src="/files/gJrcD1aPtsIFksylA9yW" alt=""><figcaption></figcaption></figure>

If you see a screen like the one below, you're all set ✅

<figure><img src="/files/6GXfW1fdWKJdHNLpyOWk" alt=""><figcaption></figcaption></figure>

**Step 8:** To check if you’re connected, navigate to **Customize** > **Connectors** > verify the **status indicator for Reo Connector**.&#x20;

<figure><img src="/files/PkM73968oqs6Q2wTwkGv" alt=""><figcaption></figcaption></figure>

### **Getting started with Reo MCP X Claude connector**

Once you have successfully set up the connector, complete the following 2 steps to get started:&#x20;

**Step 1:** From a new Claude Chat, type <mark style="color:red;">`Get me started with Reo MCP`</mark>

<figure><img src="/files/MF0TuWEDOgdsPzMH8MiJ" alt=""><figcaption></figcaption></figure>

**Step 2:** When you start for the first time, Claude walks you through a short setup flow to personalize the end-to-end journey of how Reo data works for you inside Claude.&#x20;

It takes a few minutes and you can skip any step. Here's a preview of what to expect:&#x20;

<figure><img src="/files/1TYhIBKhLMALH2ZpCHcR" alt=""><figcaption></figcaption></figure>

### **FAQs**

1. #### **How to enable custom connector for your team?**

If you're on a Team or Enterprise plan and still can't access connectors, it may be because an Owner or Primary Owner hasn't enabled them for your organization yet. Enabling a connector makes it available to your team, but it doesn't automatically grant anyone access. Each person still needs to authenticate individually before they can use it. Here's how you can do that:

a. Navigate to **Organization settings > Connectors**

<figure><img src="/files/81bCSwYNWx6xcBjTi4bx" alt=""><figcaption></figcaption></figure>

b. Under connectors - Click on Add > Custom

<figure><img src="/files/r5bt39P4lzZ6u7OGS5JZ" alt=""><figcaption></figcaption></figure>

c. Enter the name and the following remote URL <mark style="color:red;">`https://mcp.reo.dev/mcp`</mark>\
Then, click on Add.

<figure><img src="/files/LTwCfCRNYGC3B8WXPXGs" alt=""><figcaption></figcaption></figure>

Once enabled at the org level, individual users can connect the Reo MCP server with the following steps:

{% hint style="info" %}
**Note: To complete this step, it is mandatory that every user must have logged out of Reo account.**&#x20;
{% endhint %}

a. Go to Settings > Connectors\
b. Locate the Reo Connector > Click on Connect\
c. Complete the authentication flow

<figure><img src="/files/eZfTiGrfCyzdvi5ZfK8O" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: Custom connector tool access is controlled at the organization level. If the org owner has set access to “Needs approval,” individual members cannot change it to “Always allow” from their own accounts. The “Always allow” permission can only be enabled by the org owner.
{% endhint %}

2. #### **Can you add custom connectors on a free Claude plan?**

The Free plan supports only 1 connector. If you've already added a connector, you'll need to either remove it to add Reo's connector, or upgrade to a higher plan.<br>

3. #### **My connection isn’t working - what should I do?**

Before going through the authentication flow, make sure you're logged out your Reo account. If you're logged in, the connection will fail. Log out of Reo first, then try authenticating the connector again. In case the problem still persists - please reach out to your account manager or drop us an email at <support@reo.dev>

### Reo.Dev X Claude Skills

We’ve created a few ready-to-use skills for Claude. Instead of querying raw data, you get named skills and slash commands built around winning developer GTM workflows.

#### **How to add skills to Claude**

1. Open the Claude desktop app > from the left navigation menu > select **Customize**

<figure><img src="/files/7LiMlGhzaZHxtqI0eSY2" alt=""><figcaption></figcaption></figure>

2. A pop-up modal will open up. Under Customize > select **Skills**

<figure><img src="/files/ufnklQke5Na4PmpI4Z4j" alt=""><figcaption></figcaption></figure>

3. From the top-right corner > click **Add** > **Upload a skill**

<figure><img src="/files/izkwaTcJpt4wPdvwb0pN" alt=""><figcaption></figcaption></figure>

4. **Upload the skill files** we have shared, and you're all set.&#x20;

<figure><img src="/files/rYtnbwf4mORYOSFM7Q8k" alt=""><figcaption></figcaption></figure>

Once done, the skills and commands become available immediately via the `/` slash command menu.

Here are the different Claude Skills and how you can use them:

**#1 Daily Account Prioritizer: Build a hot accounts list for daily outreach**

It gives SDRs and AEs a prioritized list of accounts to focus on each day, ranked by context and a recommended action per account. No more manual signal triage every morning.

To use this:

1. Open Claude > Start a new chat
2. Select the Reo.Dev plugin
3. Type /hot-account-list

Download the skill file below:&#x20;

{% file src="/files/u0TP87LSjRcXu7mEvjaf" %}

**#2 Account Research**

Use this to generate a full account intelligence brief for any company based on developer activity data, hiring signals, competitive context, and recent news into a single view. Ideal for pre-meeting prep or territory reviews or when you simply need complete context on an account instantly.

To use this:

1. Open Claude > Start a new chat
2. Select the Reo.Dev plugin
3. Type /account-research

Download the skill file below:&#x20;

{% file src="/files/jspIZqKQCeJbqzwVfROC" %}

**#3 Sales Call Prep**

Turns your day's calendar into per-meeting prep cards, with an attendee-level brief for each customer-facing call — ready before you enter the meeting. This streamlines meeting prep and ensures you enter every meeting prepared.

To use this:

1. Open Claude > Start a new chat
2. Select the Reo.Dev plugin
3. Type /call-prep

Download the skill file below:&#x20;

{% file src="/files/currJtUWgA89fouIzhBp" %}

**#4 Engineering Org Chart**

Build a visual org chart for any target account from CTO/VP Eng down to ICs, grouped by sub-team (Backend, Frontend, DevOps, AI/ML, Security, etc.) or location, with developer activity signals overlaid.

To use this:

1. Open Claude > Start a new chat
2. Select the Reo.Dev plugin
3. Type /engineering-org-chart

Download the skill file below:&#x20;

{% file src="/files/OQCDBl7HHAvWziEfqqgR" %}

**#5 Buyer intelligence**

Drop in a list of your target accounts and the buyer persona you're targeting. Reo enriches the accounts, finds the right buyers, and reveals verified email IDs. From there, you can ask Claude to draft outreach or run campaigns.

To use this:

1. Open Claude > Start a new chat
2. Select the Reo.Dev plugin
3. Type /Reo-buyers

Download the skill file below:&#x20;

{% file src="/files/Lb1GAI4oYSVEdyZFmnFV" %}

Here's how you can automate your entire prospecting workflow in Claude, using Reo's data:&#x20;

{% embed url="<https://reo-dev.portal.trainn.co/share/ad4NI65C0gRyLl6pOGgwAA>" %}

### Prompt Guide 101

A curated set of prompts covering the 8 highest-leverage use cases. Copy, paste, customize for your workflow.

[Get the guide!](https://39628812.fs1.hubspotusercontent-na1.net/hubfs/39628812/Reo%20x%20Claude%20Connector%20Use%20Cases%20\(1\).pdf)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.reo.dev/reo.dev-claude-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
