TengoChatDevelopers

Use TengoChat in Claude, ChatGPT and Cursor

TengoChat's MCP server: add one address, sign in, and your AI app can use your agents, models, docs and files.

TengoChat runs its own MCP server. Add one address to Claude, ChatGPT, Cursor, VS Code or any other MCP app, sign in to TengoChat, and the app can talk to your agents, build new ones, ask the models, search these docs, keep files and check your credits, right where you work.

Server address
https://tengochat.com/mcp

The same address and sign-in work in every app. Your account, your agents and your credits are the ones in Create, Developers, MCP, where you also see the apps you connected and can disconnect any of them.

Claude

  1. In Claude, open Customize, then Connectors.
  2. Choose Add custom connector, paste https://tengochat.com/mcp and choose Add.
  3. Choose Connect next to it, then Allow on the TengoChat page that opens.

This works on claude.ai, the desktop app and the mobile app. On Team and Enterprise plans an Owner adds it once in Organization settings, Connectors (Add, then Custom), and each person connects with their own account in Customize, Connectors. Claude identifies itself by its published address, so there is nothing else to fill in.

Claude Code

Terminal
claude mcp add --transport http tengochat https://tengochat.com/mcp

Then type /mcp in Claude Code, choose tengochat and sign in. To use an API key instead of signing in, add --header "Authorization: Bearer $TENGOCHAT_API_KEY" to the command.

ChatGPT

  1. In ChatGPT on the web, open Settings, Security and login, and turn on Developer mode (on the plans that offer it; in a workspace, an admin may need to allow it).
  2. Open Plugins, choose +, then Add custom MCP server. Name it TengoChat and paste the server address.
  3. Choose OAuth, confirm the warning, choose Create as a plugin and install it, then Allow on the TengoChat page that opens.

Cursor and VS Code

Add the server to ~/.cursor/mcp.json (or .cursor/mcp.json in a project), or to .vscode/mcp.json in VS Code. Both ask you to sign in the first time they connect.

{
    "mcpServers": {
        "tengochat": {
            "url": "https://tengochat.com/mcp"
        }
    }
}

Any other app, or with an API key

Any MCP app that connects over HTTP can use the address. Apps that support signing in open the TengoChat page by themselves. An app that cannot sign in can send an API key instead:

mcp.json
{
    "mcpServers": {
        "tengochat": {
            "url": "https://tengochat.com/mcp",
            "headers": {
                "Authorization": "Bearer <your key>"
            }
        }
    }
}

The tools

ToolWhat it doesCost
list_agentsYour agents: id, name, what each does, model, tools, public page.Free
get_agentOne agent in full, with its instructions and starter questions.Free
chat_with_agentSend a message to an agent and get its answer. Pass thread_id to carry on.Credits for the tokens (and tools) used
create_agentA new agent from a name and instructions, optionally from a template.Free
update_agentChange an agent: instructions, model, tools, starters, memory, public page.Free
askOne answer from a model, without an agent.Credits for the tokens (and tools) used
list_modelsThe models, what each is good at, and their prices.Free
search_docsThe most relevant parts of these docs, with links.Free
list_filesYour stored files and their addresses.Free
upload_fileKeep a file (text or base64, up to 10 MB) and get its link.Free
delete_fileDelete a stored file.Free
get_accountCredits left, this month's use, storage.Free

Apps read each tool's description and ask you before using ones that change things or spend credits. Errors come back as text the model can read (an unknown agent, a missing field), so it can correct itself.

How signing in works

  • OAuth 2.1 with PKCE (S256). The server's metadata is at https://tengochat.com/.well-known/oauth-protected-resource/mcp, and the sign-in server's at https://tengochat.com/.well-known/oauth-authorization-server.
  • Apps identify themselves with a Client ID Metadata Document (their own https address) or register with Dynamic Client Registration. The page you allow shows where the app sends you back, and warns when that is your own computer.
  • One scope, mcp: the app works on your developer account. It never sees your password, your companions or your chats.
  • Access tokens last an hour. Refresh tokens last two months and change each time they are used. Disconnect an app in Create, Developers, MCP and everything it holds stops at once.

Protocol

  • Streamable HTTP at https://tengochat.com/mcp: one JSON-RPC message per POST, answered with JSON. No stream to open with GET, no sessions.
  • MCP 2026-07-28 (every request carries its version, server/discover says what is here) and the earlier versions that start with initialize: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05.
  • Every request needs Authorization: Bearer with a token from signing in or an API key. Without one the answer is 401 with WWW-Authenticate pointing at the metadata, which is what starts the sign-in in apps.
cURL
curl https://tengochat.com/mcp \
  -H "Authorization: Bearer $TENGOCHAT_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2026-07-28" \
  -H "Mcp-Method: tools/call" \
  -H "Mcp-Name: list_agents" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call",
       "params": {"name": "list_agents", "arguments": {},
         "_meta": {"io.modelcontextprotocol/protocolVersion": "2026-07-28",
                   "io.modelcontextprotocol/clientCapabilities": {}}}}'

Limits and costs

  • Each connected app has the same limit as an API key: 60 tool calls a minute. Give one a monthly spending limit in the console.
  • chat_with_agent and ask pay for the tokens they use from your credits, like the API. Everything else is free.
  • If a tool answers "Update in progress. Please check back in a few minutes.", the AI is being updated: try again in a few minutes.