Other MCP client install

Configure the TextTree MCP Server

Connect TextTree, verify the server-observed MCP connection, then send the first eligible sandbox SMS before choosing paid continuation.

Start install

Direct answer

configure TextTree MCP server

Configure TextTree in another MCP client by adding the remote server URL, using OAuth when supported, and granting only the required scopes. This page documents generic MCP transport and authentication setup.

Primary action

Connect your MCP client to https://api.texttree.ai/mcp

Other MCP client configuration

Add TextTree as an MCP server

{
  "name": "texttree",
  "url": "https://api.texttree.ai/mcp",
  "authorization": "Bearer ${TEXTTREE_BEARER_TOKEN}"
}

Expected result

A connected agent with scoped access, activation status, and a path to send the first SMS through TextTree safety and billing gates.

OAuth or token fallback

Use OAuth when supported; otherwise configure a reveal-once scoped bearer token locally.

Fallback variable: TEXTTREE_BEARER_TOKEN

Requested scopes

MCP read access, explicit execute access for allowed tools, and onboarding status for activation handoff.

Connect and verify

Read texttree://activation/status from the MCP client

Server-observed MCP initialize or discovery

Fast Send Sandbox

Eligible accounts can send one constrained first SMS before funding.

Paid continuation

Add balance for continued Fast Send or create Agent Identity for a dedicated number with inbound replies.

Troubleshooting