Skip to main content
The Text Model Context Protocol (MCP) server enables AI assistants to interact with Text features and data directly. This integration allows AI agents to perform real-time customer support operations and automate workflows without manual intervention.

What is MCP?

Model Context Protocol is an open standard that enables AI assistants to connect to external tools and data sources securely. Text’s MCP server is built upon our Workflows feature and provides functions that let AI agents take various actions in the Text ecosystem. In practice, this means an AI assistant can perform tasks such as replying to a chat, updating a ticket, or pulling a report, all within the context and permissions of a real user. All actions are limited by your token scopes and your Text account permissions, including access to tickets.

How MCP works

Text hosts a remote MCP server that follows the authenticated MCP specification. When an AI tool or application connects to this server, the interaction flows as follows:
  1. Connect: The AI assistant, or client application, initiates a connection to the Text MCP server at the given URL.
  2. Authenticate: The user is authenticated. The connection uses the same access controls as their Text account.
  3. Authorize and interact: Once authenticated, the AI assistant can invoke the available tools (API-like actions) to retrieve or manipulate Text data within your permissions.
  4. Live connection: The MCP connection remains open to stream results and receive real-time updates as needed. This allows AI assistants to maintain context and respond promptly.

Connecting to Text MCP

Text provides integrations for Claude and ChatGPT. You can also connect compatible MCP clients directly to https://mcp.text.com/v2/. Each connection uses your Text account and respects your permissions.

Claude

Connect Claude to Text through the Text integration in Claude’s directory.

ChatGPT

Connect ChatGPT to Text through the Text integration in ChatGPT’s plugin directory.

Using MCP-remote

The Text MCP external server supports public authentication for all compatible MCP clients. External clients connect via mcp-remote to the public endpoint: To start mcp-remote, you must specify a local port. The MCP client is then configured to connect to the local address using the chosen port. You can connect to Text MCP through the following ports:
  • 6274
  • 53531
  • 59123
  • 60222

Configuration example

Below is a generic example of an mcp-remote OAuth connection. Setup details may vary between versions and providers, so always refer to your specific LLM provider’s official documentation for the most up-to-date configuration instructions.

User permissions

All actions and data access are limited to the authenticated user’s roles, teams, and resource permissions. AI assistants connected through MCP use the same security model as the user.

Available MCP tools

The external Text MCP server exposes a predefined set of tools that an AI assistant can use. Each tool maps to one or more Text API calls. Access depends on the scopes required by those APIs, your account roles, and your resource permissions. For general rules on scopes, see Scopes. The below tools represent the external MCP capabilities.

Chats

Tickets

Ticket tools require an agent or administrator role and access to the relevant resources.

Customers

Agents

Accessing ticketing agents with agents-resolve also requires an agent or administrator role and the relevant resource permissions.

Reports

Language detection