> 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-mcp-connectors.md). # Reo.Dev MCP Connectors Reo MCP connects your Reo.Dev data to the AI tools you already use, so you can work with account and developer intelligence directly inside a chat instead of switching to the Reo.Dev app. Once connected, you can pull account research, check developer activity, prioritize your daily account list, and prep for calls, all from Claude, ChatGPT, or Cursor. ### What you can do once connected * Get account research and firmographics without leaving your chat * See which developers and accounts are showing real intent based on actual usage signals * Prioritize your day with a ranked account list based on live signals * Prep for calls with buyer and account intelligence pulled on demand ### Before you connect Every connector needs the same three things: * An active Reo.Dev account * Data-out API and Product API enabled on Reo.Dev * You logged out of your Reo.Dev account before you start (each guide explains why, and what happens if you skip it) ### Pick your tool * **Claude:** Connect Reo MCP to Claude Desktop. Comes with five ready-to-use skills and a prompt guide * **ChatGPT:** Connect Reo MCP through Developer Mode in ChatGPT Desktop * **Cursor:** Connect Reo MCP through Cursor's MCP settings ### Support Stuck on something? Reach out to [**support@reo.dev**](mailto:support@reo.dev) or [book time with us](https://calendly.com/chhavi-reo/30min) for hands-on help. --- # 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-mcp-connectors.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.