TellTell
Sign inGet started

AI tools and connections · 6 min

Connect Claude, Codex, Cursor, or Grok Bot

Connect your AI assistant to TellTell, choose permissions, and manage access.

Updated September 18, 2026

Before you connect

You must be an Admin of the TellTell account. Each person connects with their own TellTell sign-in and chooses the account and permissions to share. Manual MCP setup does not require a public marketplace listing.

TellTell MCP server URL

Use Streamable HTTP and the tool’s OAuth sign-in flow. Do not enter an API key or override the client ID or client secret.

https://telltell-web-789927640952.us-east1.run.app/mcp

Claude Code and Claude

Add TellTell to Claude Code
claude mcp add --transport http telltell https://telltell-web-789927640952.us-east1.run.app/mcp

Run /mcp inside Claude Code, choose TellTell, and authenticate. The command uses the current project’s local configuration. Add --scope user if you want the server available across your projects.

For Claude’s remote custom connectors on web or Desktop, open the connector settings, choose Add custom connector, and enter the MCP URL above. Team or Enterprise owners may need to add it for their organization first. Complete the TellTell sign-in and consent screen.

Claude Code MCP instructions · Claude custom connector instructions

Codex

Add and authenticate TellTell
codex mcp add telltell --url https://telltell-web-789927640952.us-east1.run.app/mcp
codex mcp login telltell

You can also add a Streamable HTTP server in the desktop or IDE MCP settings, enter the URL, and choose Authenticate. Local Codex clients on the same host share MCP configuration. Adding a local MCP server does not install a plugin in a hosted ChatGPT session.

Official Codex MCP instructions

Cursor

Add TellTell in Cursor’s MCP settings, or merge this server into your existing mcpServers configuration. Keep your other server entries. Use .cursor/mcp.json for a project or ~/.cursor/mcp.json for your user configuration.

Cursor MCP configuration
{
  "mcpServers": {
    "telltell": {
      "url": "https://telltell-web-789927640952.us-east1.run.app/mcp"
    }
  }
}

Enable TellTell and complete sign-in. Cursor cloud agents have their own custom MCP configuration and per-user OAuth; connecting Cursor desktop does not automatically connect a cloud agent.

Official Cursor MCP instructions

Grok Bot

Ask your Bot to connect
Add a remote MCP server named TellTell at https://telltell-web-789927640952.us-east1.run.app/mcp. Use Streamable HTTP, OAuth discovery, and automatic client registration with no client ID override. Show me the sign-in card. Request People and groups read permissions for the initial check. After I authorize, list tools and verify permissions before reading account data.

Complete the connect card and TellTell consent. Approval of the request in chat alone does not complete OAuth. TellTell is waiting for Cursor Marketplace approval as of September 18, 2026. While approval is pending, use the direct connection above. Once approved and listed, you can install TellTell from Plugins → Browse.

Official Grok Bot plugin instructions

Check permissions and manage connections

  1. Confirm the account

    Sign in as an Admin, confirm the intended TellTell account, and review permissions before allowing access.

  2. Verify the connection

    Ask the tool to list available TellTell tools and report the granted permissions and bulk-edit setting. Then try a small read, such as listing five groups.

  3. Review access in Settings

    Open Settings → Connections. Grok Bot has its own section. Other tools contains Setup, My account, All accounts, and Activity. My account shows your active connections; All accounts lets an Admin review or revoke connections across the account, including revoked entries.

To end access immediately, revoke the connection in TellTell Settings. Removing a server or logging out in the AI tool does not replace TellTell revocation. Activity records operations and outcomes without exposing directory payloads or credentials.

If connection fails

  • A 401 response before sign-in is the expected OAuth challenge. Finish authorization in the browser. A 404 is not expected: check that the URL ends in /mcp and matches the URL above.
  • If the tool says authorization is required, reopen its connect card. Approving an action in chat does not grant TellTell access.
  • For an invalid redirect or expired authorization link, remove any manually supplied client ID, restart the connection, and use a fresh sign-in link. Do not copy callback values from another tool.
  • If no tools appear after consent, check the granted scopes and whether the connection was revoked. Reconnect for additional scopes rather than reusing credentials from a different client.

Keep going