Looking for the AI assistant built into Reevo? That’s Ask Reevo. Use Ask Reevo to chat with your data without leaving Reevo. Use the MCP server when you want your own external agent to reach into Reevo.
- Accounts
- Contacts
- Opportunities and pipelines
- Meetings
- Tasks
- Notes
- Custom objects
- Email threads
- Users
Things You Can Ask Your Assistant to Do
Once connected, you can prompt your assistant for things like:- Pipeline reviews - “Which open opportunities have not had engagement in 14 days and have a close date this quarter?”
- Account and contact lookup - “Find all contacts at Stripe and tell me who owns the account.”
- Activity summaries - “Summarize the last three meetings on the Acme deal.”
- Pipeline movement - “Move the Globex opportunity to Negotiation and set the amount to $48,000.”
- Notes and tasks - “Log a note on the Acme opportunity summarizing today’s call, and create a follow-up task for me on Friday.”
- Custom objects - “List every record in our partner_program custom object that is in the Tier 1 segment.”
Setting Up the Connection
Before You Start
You will need an active Reevo account in the workspace whose data you want the assistant to access, plus an MCP-compatible AI client. Reevo MCP works with any client that supports MCP’sstreamable-http transport with OAuth 2.0 authorization. This includes Claude Desktop (Custom Connectors), Claude.ai (Connectors), Cursor, and ChatGPT Developer Mode connectors.
The MCP server URL is:
https://mcp.reevo.ai/mcp
Connect from Claude
- Open the Claude desktop app or the web app and sign in.
- In the left sidebar, click Customize.
- Open the Connectors section.
- Click the + button, then click Add custom connector.
- Fill in the connector form:
- Name:
Reevo - Remote MCP server URL:
https://mcp.reevo.ai/mcp
- Name:
- Click Add. Claude opens your browser to Reevo’s login.
- Sign in to Reevo with the account whose data you want the assistant to access, then click Authorize to grant access. The authorization page lists each scope the client is requesting. See Permissions and Scopes below for what each scope grants.
Connect from ChatGPT (Developer Mode)
- In ChatGPT, open Settings > Apps > Advanced settings and enable Developer Mode.
- From the Apps screen, click Create app.
- Enter
Reevoas the name andhttps://mcp.reevo.ai/mcpas the server URL. - Save the app, then complete the Reevo sign-in and authorization prompt. The authorization page lists each scope the client is requesting. See Permissions and Scopes below for what each scope grants.
Connect from Other MCP Clients
Any client that supports MCP’sstreamable-http transport with OAuth 2.0 can connect, including Cursor. The steps vary by client, but the pattern is the same:
- Find the client’s MCP or connector settings and add a new remote server.
- Enter
https://mcp.reevo.ai/mcpas the server URL. - Complete the Reevo sign-in and click Authorize when your browser opens Reevo’s login page.
Verify Your Connection
After connecting, confirm everything works with a quick test. Ask your assistant: “Which Reevo user am I connected as?” The assistant should reply with your Reevo user and organization. If it cannot answer, see the Troubleshooting / FAQs section below.Permissions and Scopes
Reevo MCP uses OAuth 2.0 with granular scopes. When you connect, Reevo’s authorization page shows exactly which scopes the client is requesting, each tied to an object type and an action (read, create, or update). The assistant can only call a tool if you granted the matching scope at sign-in. Scopes follow averb:resource format. The scopes used by the published tools are:
read:account,create:account,update:accountread:contact,create:contact,update:contactread:opportunity,create:opportunity,update:opportunityread:pipelineread:meetingread:task,create:task,update:taskread:note,create:noteread:custom_object,create:custom_object,update:custom_objectread:sequence,update:sequenceread:email_account
read:account scope rather than a dedicated scope: search_users, search_email_threads, and get_object_schema all require read:account. search_activity_timeline requires the read scope for each activity type it returns (read:meeting, read:task, read:note, read:email_account), all of which are already listed above. whoami requires no scope and is available to any connected user.
Your Reevo permissions still apply on top of OAuth scopes. Granting a scope does not let the assistant see or change anything your own account cannot.
The Tool Catalog
The default Reevo MCP catalog publishes 30 tools, each gated by a granular OAuth scope. The assistant can only call a tool if you granted the matching scope at sign-in. Operators can publish a narrower or broader catalog per organization. This catalog is an early release and will continue to change as coverage expands.Accounts
| Tool | Scope | What it does |
|---|---|---|
search_accounts | read:account | Find accounts by name, domain, owner, ICP fit, industry, or any custom field. Returns paginated summaries with links back into Reevo. |
get_accounts | read:account | Fetch the full record for one or more accounts by ID, including custom fields and related data. |
create_accounts | create:account | Create one or more accounts with name, domain, owner, and custom fields. |
update_accounts | update:account | Update fields on existing accounts (owner, segment, custom fields, and so on). |
Contacts
| Tool | Scope | What it does |
|---|---|---|
search_contacts | read:contact | Find contacts by name, email, title, role, account, or custom field. |
create_contacts | create:contact | Create contacts and link them to accounts and opportunities. |
update_contacts | update:contact | Update contact fields, ownership, and account or opportunity associations. |
Opportunities and Pipelines
| Tool | Scope | What it does |
|---|---|---|
search_opportunities | read:opportunity | Find opportunities by stage, amount, owner, account, close date, or custom field. |
create_opportunities | create:opportunity | Create new opportunities on an account, with stage, amount, close date, and custom fields. |
update_opportunities | update:opportunity | Update opportunity fields other than stage (amount, close date, owner, custom fields). |
update_opportunity_stages | update:opportunity | Move opportunities through pipeline stages, respecting your pipeline’s stage rules. |
list_pipelines | read:pipeline | List the opportunity pipelines and their stages configured in your workspace. |
Meetings
| Tool | Scope | What it does |
|---|---|---|
search_meetings | read:meeting | Find meetings by date, attendees, account, opportunity, recording status, or transcript presence. |
Activity
| Tool | Scope | What it does |
|---|---|---|
search_activity_timeline | read:meeting, read:task, read:note, read:email_account | Return a chronological activity timeline (meetings, tasks, notes, and emails) for an account or opportunity. |
Tasks
| Tool | Scope | What it does |
|---|---|---|
search_tasks | read:task | Find tasks by owner, due date, status, account, or opportunity. |
create_tasks | create:task | Create tasks and link them to accounts, contacts, or opportunities. |
update_tasks | update:task | Update task status, owner, due date, or description. |
Notes
| Tool | Scope | What it does |
|---|---|---|
search_notes | read:note | Find notes by content, author, account, contact, or opportunity. |
create_notes | create:note | Log a note on an account, contact, or opportunity. |
| Tool | Scope | What it does |
|---|---|---|
search_email_threads | read:account | Find email threads by participants, subject, account, or opportunity. |
list_mailboxes | read:email_account | List the email accounts the current user can send from, with status, health score, and daily quota and usage. Admins see all mailboxes in the organization; non-admins see only mailboxes they own. Used to pick a sender before enrolling contacts in a sequence. |
Sequences
| Tool | Scope | What it does |
|---|---|---|
search_sequences | read:sequence | Find sequences by ID, owner, status (DRAFT, ACTIVE, INACTIVE, TERMINATED), or performance metrics (open, click, or bounce rate). Optionally enriches results with each sequence’s ordered steps and A/B variants. |
enroll_in_sequence | update:sequence | Enroll contacts (by ID list or contact-list ID) into a sequence to start outreach. Sends are distributed round-robin across one or more mailboxes selected from list_mailboxes. |
unenroll_from_sequence | update:sequence | Remove contacts from a sequence, stopping all future outreach steps. |
Custom Objects and Schema
| Tool | Scope | What it does |
|---|---|---|
search_custom_object_records | read:custom_object | Find records in a custom object by any field defined on that object. |
create_custom_object_records | create:custom_object | Create records in a custom object. |
update_custom_object_records | update:custom_object | Update fields on existing custom object records. |
get_object_schema | read:account | Inspect the schema (fields, types, allowed values) for any standard or custom object. |
Workspace
| Tool | Scope | What it does |
|---|---|---|
search_users | read:account | Find users in your Reevo workspace by name, email, or role. |
whoami | None | Return the connected user and organization context. Requires no scope; always available to a connected user. |
Troubleshooting / FAQs
How is the MCP server different from AskReevo?
How is the MCP server different from AskReevo?
AskReevo is the conversational assistant built into the Reevo product. The MCP server is what connects an external assistant, such as Claude or ChatGPT, to your Reevo workspace. Use AskReevo to chat with your data inside Reevo, and use the MCP server when you want your own outside agent to read from and write to Reevo.
Does the assistant get access to everything in my workspace?
Does the assistant get access to everything in my workspace?
No. Two layers apply. First, the assistant can only call a tool if you granted the matching OAuth scope when you connected. Second, every call runs as your user and respects your existing Reevo permissions, so the assistant cannot see or change anything your own account cannot.
Can I limit which actions the assistant can take?
Can I limit which actions the assistant can take?
Yes. At sign-in, Reevo’s authorization page lists each requested scope by object type and action (read, create, update). You grant only the scopes you are comfortable with, and the catalog your organization publishes can be narrower than the default set.
Why does authorization fail or the connection not complete?
Why does authorization fail or the connection not complete?
Why does the assistant get a permission error on some requests?
Why does the assistant get a permission error on some requests?
Two layers can block a call. If you did not grant the matching OAuth scope at sign-in, the tool is unavailable; reconnect and grant the scope to enable it. If the scope was granted but your own Reevo role does not allow the action, the call fails the same way it would if you tried it in Reevo directly; ask your Reevo admin about your role’s permissions.
How do I change which scopes I granted?
How do I change which scopes I granted?
Scopes are set during the OAuth sign-in. To change them, remove the Reevo connector from your AI client, add it again, and grant the new set of scopes on Reevo’s authorization page.
How do I disconnect or revoke access?
How do I disconnect or revoke access?
Remove the Reevo connector from your AI client to stop new calls. Your Reevo administrator can also disable MCP access for the organization, which cuts off existing connections on their next call.
Still have questions? Sign in and use Ask Reevo for instant answers or to raise a support ticket.