> 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/integrations/how-to-integrate-open-docs-mcp-gateway.md).
# How to integrate Open / Docs MCP Gateway
This guide explains how to integrate your existing MCP server with Reo.Dev using the MCP Intent Gateway. The gateway integration is lightweight, non-intrusive, and does not require any changes to developer workflows or IDE configurations beyond updating the MCP endpoint.
{% hint style="info" %}
**Looking for the product/authenticated MCP integration?** If your MCP is behind OAuth or login, see the existing [**How to integrate product/authenticated MCP Gateway with Reo.Dev**](https://docs.reo.dev/integrations/input-sources/developer-insights/how-to-integrate-product-authenticated-mcp-with-reo.dev) guide.
{% endhint %}
***
### Overview
The **MCP Intent Gateway** is a proxy layer that sits between your public MCP endpoint and your actual MCP server. It allows you to observe MCP traffic and capture developer intent signals, while transparently forwarding all requests to your backend MCP server.
At a high level, the gateway enables you to:
* Expose a clean, branded MCP endpoint under your own domain
* Transparently forward requests to your underlying MCP server
* Capture intent signals such as query text and source IP
* Attribute anonymous activity to accounts once correlation is possible
All of this happens without modifying your MCP server or breaking existing IDE integrations.
***
### How the Integration Works
Instead of IDEs or agents calling your MCP server directly, they call an MCP endpoint hosted on your own domain. That endpoint routes traffic through the Reo.Dev MCP Intent Gateway, which then forwards requests to your MCP server.
#### Request Flow
1. A developer or agent issues an MCP query from an IDE (for example, Cursor or VS Code).
2. The request is sent to your public MCP endpoint (for example, `https://docs.yourcompany.com/mcp`).
3. The request reaches the Reo.Dev MCP Intent Gateway.
4. The gateway:
* Captures metadata such as query payload, source IP, and timestamp
* Securely stores the intent signal
* Forwards the request to your MCP server
5. Your MCP server processes the request and returns the response to the IDE.
This flow is fully transparent to developers.
***
### Prerequisites
Before starting, ensure you have:
* **A working MCP server** that responds to MCP queries
* Supported options: Mintlify, GitBook, [Kapa.AI](http://Kapa.AI), or custom-built servers
* **Access to your domain's DNS or proxy settings**
* **Ability to share MCP endpoint details with your developers**
**Recommended:** If you're starting from documentation, use [Kapa.AI](https://www.kapa.ai/) to convert your docs into a functional MCP server with minimal setup.
***
### Integration Steps
Before starting, ensure you have:
* A working MCP server with a stable public URL
* Control over DNS or routing for the domain where you want to expose your MCP endpoint
* An active Reo.Dev account with MCP Intent Gateway access.
***
### Integration Steps
#### Step 1: Share Your MCP Server URL
Provide Reo.Dev with your current MCP server URL.
**Example:**
`https://mcp-server.yourprovider.com`
This is the backend server that will continue handling all MCP requests.
#### Step 2: Choose Your Public MCP Endpoint
Decide on the MCP endpoint URL you want developers to use. This should be under your own domain.
**Example:**
`https://docs.yourcompany.com/mcp`
This becomes the endpoint developers will add to their IDE configurations.
#### Step 3: Map Your Endpoint to Reo.Dev's Gateway
Reo.Dev will provide you with a gateway URL. You'll need to route traffic from your chosen endpoint to this gateway using one of these methods:
* **DNS configuration** (CNAME record)
* **Reverse proxy** (nginx, Apache)
* **Platform routing** (Webflow, Vercel, Netlify settings)
Once configured, all traffic to your MCP endpoint flows through Reo.Dev's gateway, which captures intent signals before forwarding requests to your MCP server.
#### Step 4: Update Developer IDE Configurations
Share the new MCP endpoint with your developers. They'll add it to their IDE configuration—no other changes required.
**For Cursor Users**
Add this to `.cursor/mcp.json`:
```
// {
"mcpServers": {
"your-mcp-name": {
"type": "http",
"url": "https://docs.yourcompany.com/mcp"
}
}
}
```
**For VS Code Users**
**Requirements:** VS Code 1.102+ with GitHub Copilot enabled
Create `mcp.json` in your workspace's `.vscode` folder:
```
// {
"servers": {
"your-mcp-name": {
"type": "http",
"url": "https://docs.yourcompany.com/mcp"
}
}
}
```
***
#### What Data Is Captured
The MCP Intent Gateway captures high-signal metadata, including:
* MCP query payloads
* Source IP and network context
* Timestamp and request frequency
Over time, Reo.Dev correlates this anonymous activity with known accounts as additional signals become available.
***
#### How to View This Data in Reo.Dev
Head to the activity timeline of an account. Under filters, select **Activity Type-> Documentation -> Copied AI Content**
***
#### Why Use the MCP Intent Gateway
In an IDE- and agent-driven world, MCP queries represent early and high-intent signals. Integrating with the MCP Intent Gateway allows you to:
* Understand developer evaluation behavior before sales engagement
* See which accounts are exploring specific capabilities
* Power DevGTM, product analytics, and sales intelligence with MCP-level intent data
All without disrupting developer experience.\
***
#### Troubleshooting Tips
* If requests fail, verify that your routing correctly forwards traffic to the Reo.Dev gateway.
* Ensure HTTPS is enabled on your public MCP endpoint.
* Confirm that no authentication or middleware is blocking proxy requests.
For additional help, contact your assigned customer success team.
***
#### FAQs
**1. Is there a security risk with this integration?**\
No, there is no security risk. Developers will explicitly configure the MCP endpoint in their IDEs, and we do not store any confidential or sensitive information.
**2. Will we get all the queries developers are asking?** \
We surface queries only when we are able to reliably associate them with identified accounts.
**3. How should we ask developers to install the MCP in the IDE?** \
Developer can be prompted on the docs to add the MCP on the IDE.
---
# 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/integrations/how-to-integrate-open-docs-mcp-gateway.md?ask=&goal=
```
`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.