Wrapped offers two MCP (Model Context Protocol) servers: one that reads the help center, and one that reads your own account. Both are read-only, and both use the same connection, which an owner or admin creates in the dashboard. This article covers both.
The help center server
Wrapped runs an MCP (Model Context Protocol) server at https://docs.wrappedgiftcards.com/mcp. Connect it to an AI client such as Claude Code, Claude Desktop or Cursor, and it can search and read the Wrapped help center while it answers your questions or writes code against the Wrapped API. Wrapped doesn't charge for it, and it uses the Streamable HTTP transport.
Connecting needs a connection created by an owner or admin in the dashboard, on the Pro plan and above - the same connection as the account server below, so one token covers both.
The help center MCP server reads the same articles anyone can read at docs.wrappedgiftcards.com. It has no access to your Wrapped account: it can't see your gift cards, customers, orders, settings or reports, and it can't change anything.
What it's good for
- Asking an assistant how a Wrapped feature works and getting an answer based on the current help articles, with links.
- Letting a coding assistant look up how the Wrapped API behaves (authentication, adjustments, webhooks) while it builds your integration.
- Pulling setup steps for a sales channel or integration into your own notes or runbooks.
Server details
| URL | https://docs.wrappedgiftcards.com/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer <your connection token> |
| Access | Read-only, help articles only |
Tools
| Tool | What it does |
|---|---|
search_docs | Searches the help center for articles that match a question or keywords |
get_article | Returns the full text of one article |
list_categories | Lists the help center's categories |
list_articles | Lists the articles in the help center |
Your assistant decides when to call these tools. You don't need to name them; just ask your question and mention Wrapped.
Create a connection
Both servers use the same connection token.
- Go to Settings › Integrations and API keys.
- Under Connect an AI assistant, choose Create a connection.
- Copy the commands shown. The token is shown once.
You need to be an owner or admin on the Pro plan or above. A connection lasts 30 days.
Connect Claude Code
Run this in your terminal, with your own token in place of <your connection token>:
claude mcp add --transport http wrapped-help https://docs.wrappedgiftcards.com/mcp --header "Authorization: Bearer <your connection token>"
Start a new Claude Code session and ask a question such as "Using the Wrapped help center, how do I correct a gift card balance through the API?" Run claude mcp list to check that wrapped-help is connected.
Connect Claude Desktop
Claude Desktop's Add custom connector asks only for a name and a URL: there's nowhere to put a connection token, because it signs in to a server instead. To reach Wrapped's servers, point Desktop at the mcp-remote bridge, which needs Node.js installed.
- In Claude Desktop, open Settings › Developer › Edit Config.
- Add the servers below to
claude_desktop_config.json, with your own token in place of<your connection token>. - Restart Claude Desktop, then check Settings › Developer to see that both are running.
{
"mcpServers": {
"wrapped-help": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://docs.wrappedgiftcards.com/mcp",
"--header",
"Authorization:Bearer <your connection token>"
]
}
}
}
Leave out the space after Authorization: - Claude Desktop splits arguments on spaces, which would otherwise break the header in two.
Connect Cursor
Add the server to Cursor's MCP configuration: .cursor/mcp.json in your project, or ~/.cursor/mcp.json to use it in every project.
{
"mcpServers": {
"wrapped-help": {
"url": "https://docs.wrappedgiftcards.com/mcp",
"headers": { "Authorization": "Bearer <your connection token>" }
}
}
}
Open Cursor's MCP settings to check that the server shows as connected, then ask the agent about Wrapped.
Other MCP clients
Any MCP client that supports remote servers over Streamable HTTP and lets you set a header can connect: use the URL https://docs.wrappedgiftcards.com/mcp with Authorization: Bearer <your connection token>.
A client that only runs local (stdio) servers can still reach it through the mcp-remote bridge, the same way Claude Desktop does above.
Claude on the web (claude.ai) can't connect: custom connectors there sign in to a server rather than send a token.
Connect an assistant to your account
On the Pro plan and above, owners and admins can let an AI assistant look things up in their Wrapped account: your plan and this period's gift card usage, sales channel health, a gift card's details, timeline, sync status and email delivery, recent sync errors, your automations, and how current your reports are.
It's read-only. The assistant can't issue, adjust, void or delete gift cards, or change any setting. Gift card codes are always masked to their last four characters.
Use the same connection as above (Settings › Integrations and API keys › Connect an AI assistant › Create a connection), then add this server to your AI client and ask a question such as "Why hasn't gift card ending 4F2K synced to Shopify?"
| URL | https://manage.wrappedgiftcards.com/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer <your connection token> |
| Access | Read-only, this account only |
Claude Code:
claude mcp add --transport http wrapped https://manage.wrappedgiftcards.com/mcp --header "Authorization: Bearer <your connection token>"
Cursor and other clients that accept an mcp.json with headers:
{
"mcpServers": {
"wrapped": {
"url": "https://manage.wrappedgiftcards.com/mcp",
"headers": { "Authorization": "Bearer <your connection token>" }
}
}
}
Claude Desktop: use the same mcp-remote configuration shown above, with https://manage.wrappedgiftcards.com/mcp as the URL. You can list both servers in claude_desktop_config.json at once - they share the one connection.
Anyone with the token can read your account's data until it expires. A connection lasts 30 days, and stops working sooner if the person who created it leaves your account, or your account moves to a plan without API access. To connect again, create a new one.
Common questions
Can the assistant see my gift cards or make changes to my account?
The help center server can't see your account at all, even with your connection token. The account server can read your account's data (with codes masked) but can never change anything. To change gift cards from code, use the Wrapped API.
Do I need a Wrapped account or an API key?
You need a Wrapped connection for both servers, created by an owner or admin on Pro and above. It isn't an API key: it only reads, it expires after 30 days, and it can't change anything. The help articles themselves stay readable by anyone at docs.wrappedgiftcards.com.
Does it cost anything?
Wrapped doesn't charge for it. Your AI assistant's own plan and usage limits still apply.
The assistant's answer doesn't match what I see in my dashboard. What should I do?
Check the article it quoted, and confirm in your dashboard. If something still looks wrong, contact the Wrapped team; see Getting help from the Wrapped team.
Does the assistant always get the latest articles?
Yes. The server reads the published help center, so answers are based on the articles as they are when the assistant asks.
