Connext MCP

com.rtiPublished by rti.comOfficial publisherv1.7.1Updated Oct 24, 2026

Integrate Connext AI into agentic workflows, enabling Connext product-aware assistance.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

Remote MCP endpoint that brings RTI Connext product-aware AI assistance into agentic workflows.

What you can do
  • Connects an assistant to RTI's Connext AI service for product-aware assistance.
  • The manifest lists no individual tools, so the exact operations are not documented here.
  • Intended to be used inside agentic workflows that need Connext-specific help.
When to use it
Consider it when your workflows involve RTI Connext and you want an assistant to draw on Connext product knowledge rather than generic answers. Because no tools or documentation are published, evaluate it only if you already trust the RTI-hosted service.
Requirements
A remote streamable HTTP endpoint at chatbot.rti.com; no local package or runtime is needed. OAuth authentication is required, so you need an account accepted by that service. No environment variables or headers are declared.
Before you install
The server is hosted by RTI and requires OAuth sign-in, so prompts and any data you share go to that third party. No tool list, README or instructions are published, so what it can read or change is unknown before connecting. Review the OAuth scopes requested during sign-in.

Installation

In SourceWeft

  1. Open Connext MCP in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.rti%2Fconnext-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "connext": {
      "type": "http",
      "url": "https://chatbot.rti.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.7.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.