Chat Thing
ai.chatthingPublished by chatthing.aiOfficial publisherv1.0.0Updated Oct 24, 2026
Build and manage AI-native customer support agents from Claude or any MCP client.
Overview
Lets an assistant build and manage AI-native customer support agents through a remote Chat Thing endpoint.
- What you can do
- This remote MCP server connects an MCP client to Chat Thing, a platform for AI-native customer support agents. According to the registry description, it lets the assistant build and manage those agents from Claude or any other MCP client. No individual tools are listed in the manifest, so the specific operations are not documented in the supplied material.
- When to use it
- Worth considering when a team already uses Chat Thing and wants to create or maintain its customer support agents from an MCP client instead of the web interface. It is less relevant if you do not use Chat Thing or do not manage support agents. Because no tool list is provided, confirm the available operations before relying on it.
- Requirements
- A remote MCP endpoint at over streamable HTTP. OAuth authentication is required. No environment variables, headers, or packages are declared. Network access to the provider's endpoint is needed.
Installation
In SourceWeft
- Open Chat Thing in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/ai.chatthing%2Fchat-thing/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"chat-thing": {
"type": "http",
"url": "https://app.chatthing.ai/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% 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
- 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.