C
Chatty

Model Context Protocol (MCP) Server

Chatty provides a first-class Model Context Protocol (MCP) server. With MCP, autonomous AI agents inside Claude Desktop, Cursor IDE, Claude Code, or Windsurf can inspect, configure, train, and monitor your entire chatbot fleet using natural conversation.


The 8 Core MCP Tool Suites

Chatty exposes 8 dedicated tool suites through its streamable HTTP MCP interface:


Client Configuration

Chatty's MCP endpoint is hosted at:

https://api.chatty.personaliai.com/mcp

1. Claude Desktop Setup

Edit your Claude Desktop configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "chatty": {
      "url": "https://api.chatty.personaliai.com/mcp"
    }
  }
}

2. Cursor IDE Setup

In your project root, create or edit .cursor/mcp.json:

.cursor/mcp.json
{
  "mcpServers": {
    "chatty": {
      "url": "https://api.chatty.personaliai.com/mcp",
      "headers": {
        "Authorization": "Bearer chatty_sk_your_api_key_here"
      }
    }
  }
}

3. Claude Code CLI

Add the server directly from your terminal:

Terminal
claude mcp add chatty https://api.chatty.personaliai.com/mcp

Authentication & OAuth2 Handshake

When using Claude Desktop or other dynamic clients, Chatty supports RFC 7591 Dynamic Client Registration and OAuth2 Discovery:

  1. The MCP client queries /.well-known/oauth-protected-resource/mcp.
  2. The client registers automatically and opens your browser to the Chatty authorization screen.
  3. You approve the connection with your Chatty account credentials.
  4. The client receives a scoped OAuth2 token and begins interacting with your bots.

When using developer environments like Cursor or headless CI/CD pipelines, you can pass a standard API Key (chatty_sk_...) in the Authorization: Bearer header to bypass the interactive browser login.