Revo Digital API
MCP Server
Connect advanced AI assistants directly to your Revo Digital data and tools. Query, automate, and orchestrate everything in your account with AI — in any app that supports HTTP-based MCP.
What is MCP?
MCP (Model Context Protocol) is an open protocol that standardizes how applications provide context to LLMs. The Revo Digital MCP server provides a standardized way to connect AI models to your data and tools — without worrying about internal API details.
Think of it as a bridge: you can now query, automate, and orchestrate everything in your Revo Digital account with AI, in any app that supports HTTP-based MCP (like Cursor, Windsurf, OpenAI Playground, and more). You can also build your own agent, plug in your favorite AI, and let automation and insights flow.
Quickstart Guide
1. Get Your Private Integration Token (PIT)
- Go to Settings → Private Integrations in the Revo Digital sub-account you want to use.
- Click "Create New Integration", choose the required scopes (see below), and copy the generated token.
2. Configure Your Agent / Client
Point your MCP-compatible client to the Revo Digital MCP endpoint:
https://services.leadconnectorhq.com/mcp/Add your Private Integration Token as a Bearer token in the authentication header. Here's an example JSON configuration for most MCP clients:
{
"mcpServers": {
"revo-digital": {
"url": "https://services.leadconnectorhq.com/mcp/",
"transport": "http-stream",
"headers": {
"Authorization": "Bearer YOUR_PRIVATE_INTEGRATION_TOKEN"
}
}
}
}3. Start Making Requests
- Use any compatible client or agent to send HTTP requests to the MCP server endpoint.
- You can now access Revo Digital data using natural language and tool calls.
| # | Tool Name | Endpoint | Description |
|---|---|---|---|
| 1 | Get Calendar Events | calendars-get-calendar-events | Get calendar events (requires userId, groupId, or calendarId) |
| 2 | Get Appointment Notes | calendars-get-appointment-notes | Retrieve appointment notes |
| 3 | Get All Tasks | contacts-get-all-tasks | Get all tasks for a contact |
| 4 | Add Tags | contacts-add-tags | Add tags to a contact |
| 5 | Remove Tags | contacts-remove-tags | Remove tags from a contact |
| 6 | Get Contact | contacts-get-contact | Fetch contact details |
| 7 | Update Contact | contacts-update-contact | Update a contact |
| 8 | Upsert Contact | contacts-upsert-contact | Update or create a new contact |
| 9 | Create Contact | contacts-create-contact | Create a contact |
| 10 | Get Conversations | conversations-get-conversations | Retrieve conversations for a location |
| 11 | Get Conversation | conversations-get-conversation | Fetch a single conversation by ID |
| 12 | Get Messages | conversations-get-messages | Get messages by conversation ID |
| 13 | Send a New Message | conversations-send-a-new-message | Send a message into a conversation thread |
| 14 | Get Location | locations-get-location | Get sub-account (location) details by ID |
| 15 | Get Custom Fields | locations-get-custom-fields | Retrieve custom field definitions for a location |
| 16 | Search Opportunity | opportunities-search-opportunity | Search for opportunities by criteria |
| 17 | Get Pipelines | opportunities-get-pipelines | Retrieve all opportunity pipelines |
| 18 | Get Opportunity | opportunities-get-opportunity | Fetch an opportunity by ID |
| 19 | Update Opportunity | opportunities-update-opportunity | Update an existing opportunity |
| 20 | Get Order by ID | payments-get-order-by-id | Fetch order details by unique order ID |
| 21 | List Transactions | payments-list-transactions | Paginated list, supports filtering |
| 22 | Edit Posts | social-media-posting-edit-post | Modifies an existing social media post |
| 23 | Create Posts | social-media-posting-create-post | Creates a new social media post for multiple platforms |
| 24 | Get Post | social-media-posting-get-post | Retrieves detailed information for a specific social media post |
| 25 | Get Social Media Accounts | social-media-posting-get-account | Retrieves a list of connected social media accounts |
| 26 | Get Social Media Statistics | social-media-posting-get-social-media-statistics | Retrieve analytics data for multiple social media accounts |
| 27 | Get Posts | social-media-posting-get-posts | Retrieves social media posts |
| 28 | Check Url's Slug Existence | blogs-check-url-slug-exists | Validates whether a URL slug is available for a blog post before publishing |
| 29 | Get Blog Post | blogs-get-blog-post | Retrieves blog posts for a specific blog site |
| 30 | Get Blog Categories | blogs-get-all-categories-by-location | Retrieves all blog categories for a specific location |
| 31 | Create Blog Post | blogs-create-blog-post | Creates a new blog post for a blog site |
| 32 | Get All Blog Authors | blogs-get-all-blog-authors-by-location | Retrieves all blog authors for a specific location |
| 33 | Get All Blogs | blogs-get-blogs | Retrieves a list of blog sites |
| 34 | Update Blog Post | blogs-update-blog-post | Modifies an existing blog post |
| 35 | Get Email Templates | emails-fetch-template | Retrieves email templates for a location |
| 36 | Create Email Template | emails-create-template | Creates a new email template |
Authentication & Required Scopes
For full tool access, your Private Integration Token (PIT) must include the following scopes. Alternatively, use only the View Locations scope in combination with the specific scopes required for your AI use case.
You'll be prompted to select these scopes when creating your Private Integration under Settings → Private Integrations in Revo Digital.
Integration with n8n
You can seamlessly integrate the Revo Digital MCP server with n8n to automate workflows and connect your data with hundreds of other applications.
1. Configure the MCP Client in n8n
In your n8n workflow, add the MCP client node and set the MCP URL to https://services.leadconnectorhq.com/mcp/. For the transport protocol, select HTTP Streamable, which is available in n8n v1.104 and later.
2. Set Up Authentication
Add your Private Integration Token as a Bearer token in the authentication configuration of the MCP client node.
3. Provide the Location ID
The MCP server supports dynamic locationIds. You can either hardcode it or provide it dynamically from upstream nodes in your workflow.
4. Select Your Tools
Once configured, you can select any of the available Revo Digital tools as needed for your workflow.
Sample Langgraph Agent
You can build a custom AI agent using Langgraph (or any framework) that connects to the Revo Digital MCP server. The agent discovers available tools at runtime and can chain multiple operations together in a single conversation turn.
What You Can Do with MCP
Contact Management on Autopilot
Query, tag, and organize contacts using natural language. Let your AI assistant handle the busywork.
"Show me all contacts added last week and tag them as 'New Lead'."
Conversational AI That Can Text for You
Read conversations, draft follow-ups, and send messages — all through your AI agent.
"Find all unread messages and send a follow-up: 'Hey! Just checking in — let us know if you have questions!'"
Custom Workflows & Multi-Step Automation
Chain multiple tools together in a single prompt. Create contacts, add tags, send messages, and update pipelines — all in one go.
Payment & Transaction Intelligence
Query payment data, flag anomalies, and generate financial summaries with AI.
"Show me the last 10 transactions over $100, and flag any with a refund request."
You can do much more beyond these examples. Any operation available through the Revo Digital API can be accessed via MCP.
Roadmap & Vision
The MCP server is actively evolving. Expect expanded tool coverage, deeper workflow integration, and more AI-native features as the protocol matures. Our goal is to make every Revo Digital capability accessible through natural language.
Try It Out & Share Feedback
We'd love to hear how you're using the MCP server. Have ideas, feature requests, or ran into an issue?
Send Feedback