Connect any AI agent to your help desk

Deskwoot speaks the Model Context Protocol, so OpenClaw or any MCP client can work your real queue: read, reply, draft for approval and start conversations. Every token is scoped and every action is audited.

A standard way to give an AI agent its tools

The Model Context Protocol is how a modern AI agent gets a defined set of tools it can call. Instead of writing a fragile custom integration and babysitting it, you connect an MCP client and the agent discovers exactly what it is allowed to do. For support that is the difference between a bot that drafts text in a vacuum and an agent that works inside your real help desk.

mcp.config.json
{
  "mcpServers": {
    "deskwoot": {
      "type": "http",
      "url": "https://deskwoot.com/api/mcp",
      "headers": {
        "Authorization": "Bearer dw_mcp_your_token"
      }
    }
  }
}

1. Enable the MCP server

In Deskwoot, open Settings, then MCP Server, and switch it on.

2. Create a token

Choose what the agent may do and which inboxes it can see.

3. Point your agent at the URL

Paste the connection URL and the token into your agent's settings, for example in OpenClaw. It finds its tools and starts working.

What your agent can actually do

A focused set of tools, not a master key. Your agent sees exactly these and gets to work.

  • Read and search conversations

    List, search, and read full message history across every channel the token can see.
  • Reply to customers

    Send a real reply on the original channel, attributed to the agent in the thread.
  • Leave private notes

    Drop context only your team sees, so a human picks up with everything they need.
  • Draft replies for approval

    Propose an answer that stays pending until a human approves or edits it. Nothing ships unsupervised unless you allow it.
  • Manage contacts

    Find, create, and update contacts, set custom attributes, and add notes to a profile.
  • Start outbound conversations

    Open a new thread to a customer, the tool that makes onboarding nudges, follow-ups, and outreach possible.
  • Set status, assign, label

    Move a conversation through your workflow: status, priority, labels, attributes, and escalation to a person.
  • Poll the events feed

    Ask what changed since the agent last looked, so it can react to new messages and updates.
  • Use your workspace knowledge

    Search your published help articles, fill in saved replies and read support metrics such as response times and CSAT.
  • Look up and act on orders

    Find a customer's Shopify, WooCommerce or Stripe orders and subscriptions. Refunds, cancellations and fulfillment each need their own scope on the token.
  • Work tickets

    Split a ticket off a conversation and hand it to a team or an agent, comment on it, change its status, team, category or priority, and answer the customer from it in the conversation it came from. Needs tickets switched on, and a draft only token cannot answer.

A teammate with a name badge and a leash

Letting an AI agent into your inbox should not mean handing over the keys. Here is what keeps it in bounds.

  • Scoped tokens

    Each token gets only the permissions you grant: read only, reply, manage contacts. No master key.
  • Restricted to inboxes

    Lock a token to specific inboxes, so an agent only ever touches the queues you point it at.
  • Revocable instantly

    Pull a token and the agent loses access on the spot. No waiting, no redeploy.
  • Every action audited

    The agent acts as its own service account, so every reply, note, and status change is logged to it.
  • Locked to your workspace

    Tenant isolation holds at every layer. There is no path to another company's data.
  • No double sends

    A retried send never reaches the customer twice.

What the agent can never touch

  • Change account settings or channel config
  • Touch your Deskwoot billing or payment methods
  • Delete conversations or contacts
  • Send mass broadcasts
  • Manage webhooks or export data

One connection inbound and outbound

Inbound support triage

The agent reads incoming conversations, answers the routine ones from your help center, drafts replies for the tricky ones, and escalates anything about money or a frustrated customer to a person.

Proactive outreach

Because it can start outbound conversations, the agent runs onboarding check-ins, follows up on stalled conversations and handles outreach to creators and partners, all from your real help desk.

Cover while your team is offline

An MCP agent works the queue when your team is offline, drafting and holding replies for morning review or handling the simple stuff on its own, within the limits you set.

Frequently asked questions

The short answers are here. For anything else, ask Fynn below.

What is an MCP server for customer support?

An MCP (Model Context Protocol) server exposes your help desk to an AI agent as a defined set of tools. Instead of a custom integration, the agent connects once and can read conversations, reply, draft answers, and manage contacts, within the scopes you grant.

What can the AI agent NOT do?

The MCP server leaves out account settings, billing, deleting data, mass broadcasts and webhook management. Those stay with people in the dashboard. The agent works conversations, tickets, drafts, notes and contacts. It can look up orders and refund, cancel or fulfill them only when you give its token those commerce scopes.

Is it safe to give an AI agent access to my inbox?

Tokens are scoped, can be restricted to specific inboxes, and are revocable instantly. Every action is attributed to the agent's service account in the audit log, and access is locked to your workspace with no path to another company's data.

Do I need an Enterprise plan to use MCP?

The MCP server is an Enterprise feature, and it is also available during the 7-day Enterprise trial that every new Deskwoot account starts on, so you can try it before you buy.

Put your AI agent in your inbox

Deskwoot interactive demo