MCP Server

Connect your favorite AI tools — Claude Desktop, VS Code, Cursor, Windsurf, Claude Code, and more — to Yaplet using the Model Context Protocol. Manage your entire account through natural conversation.

What Is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external services and use their tools. Yaplet exposes an MCP server so you can manage your account from any MCP-compatible client — create chatbots, write knowledge base articles, send campaign emails, manage conversations, and more, all through natural language.

Requirements: MCP access requires an active paid subscription with the Copilot feature enabled. Each tool category can be individually enabled or disabled in your organization settings.

How Authentication Works

Yaplet's MCP server supports two authentication methods:

OAuth 2.0 (Browser Login)

The default method. Just add the server URL to your client — when you connect, your browser opens a login page where you sign in with your Yaplet account, pick your organization, and approve access. Each action is traced to your personal user account, and you can choose which tool categories to grant access to.

API Key

For clients that don't support OAuth redirects (like Cursor or Antigravity), you can authenticate with your organization's API key instead. Generate one at Settings > API Settings in your dashboard, then pass it as a Bearer token in the Authorization header of your MCP config.

API key access level: API key connections act as the organization owner with access to all enabled Copilot tool categories. Treat your API key like a password — anyone with it has full MCP access to your organization.

Setup Guides

Yaplet's MCP server is available at:

https://yaplet.com/api/mcp

It uses the Streamable HTTP transport — the current MCP standard. Select your client below for setup instructions.

Claude Desktop supports remote MCP servers through its Connectors feature with automatic browser login.

Open Settings

In Claude Desktop, go to Settings > Connectors.

Add a New Connector

Click Add Connector and configure it:

  • Name: Yaplet
  • URL: https://yaplet.com/api/mcp

Log In

Your browser will open automatically. Sign in with your Yaplet account, select your organization, and approve access. That's it — no API key needed.

Start Using It

Open a new conversation and you'll see Yaplet's tools available. Ask something like "List my widgets" to verify the connection.

Older versions: If your version of Claude Desktop doesn't support Connectors yet, you can use the mcp-remote bridge as a fallback. Add this to your claude_desktop_config.json:
{
  "mcpServers": {
    "yaplet": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://yaplet.com/api/mcp"
      ]
    }
  }
}

mcp-remote will open a browser window for you to log in.

Alternative: API Key. If browser login doesn't work in your setup, you can use an API key instead. Replace the config above with:
{
  "mcpServers": {
    "yaplet": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://yaplet.com/api/mcp",
        "--header", "Authorization:Bearer yAPI_your-api-key-here"
      ]
    }
  }
}

Config file location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
Other MCP clients: Any client that supports the Streamable HTTP transport can connect to Yaplet. Point it to https://yaplet.com/api/mcp — the client will handle OAuth login automatically. If your client doesn't support OAuth redirects, pass your API key as a Bearer token in the Authorization header.

Available Tools

The MCP server exposes 20 tools organized into eight categories. Each category maps to a permission that can be enabled or disabled independently.

Data Access

Browse and inspect any resource in your organization — widgets, chatbots, conversations, contacts, and more.

Widget Tools

Create and configure chat widgets, generate install code, and connect resources like chatbots and knowledge bases.

Chatbot Tools

Set up AI chatbots, add knowledge documents, and diagnose response issues.

Help Tools

Manage knowledge bases (HTML articles) and documentation portals (Markdown pages). Create content with AI, organize with categories, and control publishing.

Conversation Tools

Read chat messages, search conversations, assign chats to agents, and send replies or private notes.

Newsletter Tools

Create email campaigns with AI content, build automation workflows, and check email performance.

Outreach Tools

Create banners, surveys, product tours, chat messages, and news releases with targeting rules.

Analytics Tools

View agent performance, chatbot effectiveness, visitor traffic, and AI token usage reports.


How Tools Work Together

Most tasks involve multiple tools working in sequence. You don't need to orchestrate this manually — just describe what you want and the AI handles the rest.

Discover

The AI starts by listing existing resources (list_records) to find IDs and understand what's already set up.

Inspect

If needed, it fetches full details of a specific resource (get_record) to check current configuration.

Act

It uses the right management tool to create, update, or configure resources. All management tools follow the same pattern: omit the id to create, provide an id to update.

Connect

Finally, it links resources together — connecting a chatbot to a widget, assigning an article to a category, or publishing content.

Example: Asking "Create a chatbot called Support Bot and connect it to my main widget" would automatically list your widgets, create the chatbot, and link it — all from a single prompt.


Privacy & Security

  • All requests are authenticated and scoped to your organization.
  • OAuth tokens are scoped to the permissions you approve during login. Actions are traced to your personal user account.
  • API key connections act as the organization owner with access to all enabled Copilot tool categories — no per-category scope restriction.
  • External callers (OAuth) cannot see private agent notes in conversations. API key callers have full access, including private notes.
  • All actions are logged and traceable to the authenticated user.