# Use from ChatGPT or Claude (MCP)

> Connect ChatGPT, Claude, Cursor or any MCP client to a Wapitick business, with the same limits as Ask Wapitick.

Wapitick runs a remote [Model Context Protocol](https://modelcontextprotocol.io) server. An AI tool connected to it can
look things up and do work in one Wapitick business: the same tools as Ask Wapitick, with the same limits.

## Connect

The connector address is `https://mcp.wapitick.com/mcp` (Streamable HTTP, stateless). It is also shown in Wapitick under
**Settings, Developers, Use from ChatGPT or Claude**.

- **ChatGPT:** Settings, then Connectors, then Add. Paste the address.
- **Claude:** Settings, then Connectors, then Add custom connector. Paste the address.
- **Cursor, Codex and other clients:** add a remote MCP server with that address.

The tool then opens a Wapitick sign-in page. Sign in, pick the business, and choose what it may do. Each connection
appears in that Settings page, where you can disconnect it at any time.

## What it may do

Tools are grouped by risk. Which ones are offered depends on your plan and your role in the business.

| Risk | Examples | What happens |
|---|---|---|
| Look up | customers, chats, orders, reports | runs straight away; nothing changes |
| Change | drafts, labels, tasks | runs straight away; can be undone |
| Message customers | send a template, reply | shown to you as a preview first |
| Spend money | broadcasts, top-ups | always needs your confirmation, inside the daily spend limit |
| Delete or stop | delete a draft, stop a broadcast | always needs your confirmation |

Anything that needs a confirmation waits in the Wapitick dashboard until you tap it. A second confirmation is only ever
accepted from the dashboard, never from the AI tool. Text that comes from customers is marked as untrusted when it is
passed back to the AI tool.

## Sign-in details

- `/mcp` uses OAuth 2.1 ([OAuth](/oauth)): the client discovers the authorization server from
  `/.well-known/oauth-protected-resource` (RFC 9728), registers itself, and uses PKCE. Tokens are issued for the MCP
  resource only and are limited by the scopes you allowed and your current role.
- `/mcp-key` accepts a Wapitick API key (`Authorization: Bearer wk_live_...` or `wk_test_...`) for scripts and
  self-hosted agents. A `wk_test_` key works only in the test workspace.

Errors are [problem codes](/errors), the same as the REST API.
