Connext MCP
Wire RTI Connext product knowledge into Claude Code or Cursor so agents answer DDS and Connext questions without leaving the repo.
Overview
Connext MCP is a MCP server for the Build phase that connects agents to RTI Connext AI over streamable HTTP for product-aware assistance.
What is this MCP server?
- Streamable-HTTP remote at chatbot.rti.com—no local npm package to ship
- Product-aware Connext AI assistance inside agentic coding workflows
- MCP schema version 1.7.1 for current MCP client configs
- Suited to teams already on RTI Connext who want docs and troubleshooting in-chat
- Registration-only setup: point the MCP client at the published remote URL
- Server version 1.7.1
- Single streamable-HTTP remote endpoint
- No local npm package in server manifest
What problem does it solve?
Agents guess at DDS and Connext APIs because product docs live outside the IDE and break flow during integration work.
Who is it for?
Solo or small-team builders on Connext who want Claude Code or Cursor wired to official Connext AI during backend and middleware work.
Skip if: Teams not using RTI Connext, or builders who need offline-only MCP with no vendor-hosted endpoint.
What do I get? / Deliverables
After you register the remote MCP URL, agents can pull Connext-focused answers while you code integrations instead of context-switching to manuals.
- Registered Connext MCP remote in the agent config
- In-session Connext product-aware answers during coding
- Reduced manual doc lookup for Connext-specific tasks
Recommended MCP Servers
Journey fit
Canonical shelf is Build because you add this remote MCP when wiring industrial or embedded agent tooling alongside your product stack. Integrations is the right subphase: streamable HTTP connects the agent client to Connext’s hosted chatbot endpoint, not local codegen or ship gates.
How it compares
Vendor-hosted product MCP remote, not a local skill file or generic web-search plugin.
Common Questions / FAQ
Who is com.rti/connext-mcp for?
Developers and indie builders working with RTI Connext who want coding agents to use Connext AI through MCP during implementation.
When should I use com.rti/connext-mcp?
Use it during Build when you are integrating or maintaining Connext/DDS code and want product-aware help inside your agent client.
How do I add com.rti/connext-mcp to my agent?
Add an MCP remote entry with type streamable-http and URL https://chatbot.rti.com/mcp in your Claude Code, Cursor, or compatible MCP settings.