Unitag
Login

Connect Unitag to Claude

Claude reaches outside services through connectors, and it takes a custom one directly. Add the Unitag address and client ID once and sign in; the connector then follows you across the Claude apps signed in to that account.

Before you start

  • A Unitag account you can sign in to. The assistant will act with that account's permissions.

  • A Claude plan that allows custom connectors. On Team and Enterprise plans a primary owner adds connectors for the whole organisation, so you may be enabling one rather than creating it.

  • The connector address and the Unitag client ID, which you can copy from the boxes below.

https://mcp.unitag.io/mcp

42deo5aspdubqjubemlal7iv54

Add the connector

  1. Open Settings and then Connectors on claude.ai. On a Team or Enterprise plan, an owner does this once in the organisation's settings.

  2. Choose Add custom connector.

  3. Name it Unitag and paste the connector address into the remote MCP server URL field.

  4. Open Advanced settings and paste the Unitag client ID into the OAuth Client ID field. Leave the client secret empty, then add the connector.

  5. Choose Connect beside the new entry. Claude opens the Unitag sign-in page: log in as usual and approve the access it asks for.

Unitag then appears as connected, and in the Claude apps — the desktop app and the mobile app — signed in to the same account.

Use it in a conversation

In a new chat, open the tools menu below the message box and check that Unitag is enabled. Then ask your question in ordinary words; Claude tells you which Unitag capability it used and what it got back.

The first time, ask for something you can check by eye — the number of QR codes in a campaign, or the destination of a code you know. It is worth seeing the answer land before you ask it to change anything.

Letting it make changes

Claude asks for permission before it uses a capability that writes, and shows you what it is about to do. Read the values in that prompt — the destination URL, the name, the campaign — rather than the sentence introducing it.

Changes made this way are real and immediate. They appear in your activity logs under your own account, and they are undone the same way any other change is.

Claude Code and Claude Desktop

The same connector works in the terminal. Claude Code adds it with one command, which carries the client ID, and the sign-in happens in your browser as usual:

claude mcp add --transport http --client-id 42deo5aspdubqjubemlal7iv54 unitag https://mcp.unitag.io/mcp

Claude Desktop picks up the connectors from your claude.ai account, so if you added it above there is nothing further to do there.

If it does not work

  • No option to add a custom connector. On Team and Enterprise plans this is an owner's setting. Ask whoever administers your Claude organisation to add Unitag once, after which it is yours to enable.

  • It stays on "connect" and never signs in. A pop-up blocker is the usual cause. Allow pop-ups for claude.ai and try connecting again.

  • Unitag is connected but never used. Check that it is enabled in the tools menu for that conversation, and name what you are asking about — a question with nothing to look up gets answered without looking anything up.

  • It says it cannot see something. The connector has your permissions. If the data is in a sub-organisation your account cannot reach, the assistant cannot reach it either.

  • The sign-in page reports an unknown or invalid client. The client ID is missing or mistyped. Remove the connector and add it again, pasting the client ID from this page.