> ## Documentation Index
> Fetch the complete documentation index at: https://www.cloudtag.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Personal connectors in groups

> Connect your own accounts on Your connectors, and the agent can use them in a group only for your requests, acting as you, once you allow it in the thread from an emailed link.

A personal connector is a service you connect for yourself. The agent can use it in a group, but only for requests **you** make, acting as you, and never for anyone else's. It's the same idea as Claude Tag's personal connectors, with Cloud Tag keeping the sign-in instead of claude.ai.

Connectors an admin sets up for a group act with an account shared by the whole group. A personal connector acts with your own account, so it's the way to let the agent read your calendar or your tickets for your own questions.

## Connect one

1. Sign in to Cloud Tag and open **Your connectors** in the header.
2. Under **Connect a service**, paste the service's MCP server URL. Services that need sign-in send you through their sign-in next.
3. Under **Organizations whose agents may use it for your requests**, tick the organizations it's for, and save. An organization appears here once you've posted in one of its groups.

## Use it

Ask the agent in a thread as usual:

```text
@cloud what's on my calendar Thursday, and does the launch review clash with anything?
```

The first time a request of yours in a thread needs one of your connectors, Cloud Tag emails you a link: **Use your … ?** Open it and choose to allow it or not. If you allow it, the agent can use that connector's read-only tools for your requests in that thread for the next day. Then ask again in the thread.

If you didn't ask for anything in that thread, choose **Don't allow**: someone may be writing as you.

### Anything that changes things asks you each time

A tool counts as read-only only when the service itself says it just reads; Cloud Tag checks with the service before each new call. Any other tool, one that creates, sends, edits or deletes something, or one the service doesn't describe, needs your OK for that one call:

1. Cloud Tag emails you **Approve … on your …?** and tells the thread it's waiting for you.
2. The link shows exactly what will run: the tool and all its arguments.
3. **Approve this call** runs it once, exactly as shown. **Decline** doesn't run it. A request you don't answer within a day isn't run.

Only you can answer: a group admin can't approve calls on your connectors. You see every argument, including any secrets, since it's your account; while it waits, Cloud Tag keeps the request encrypted. A call whose arguments can't be shown faithfully, because they're too large or contain invisible or direction-changing characters, isn't run and isn't sent to you.

## What others in the group can see

- The agent uses your connector only for messages you sent. Someone else in the thread can't get it to act as you.
- Other people's earlier messages in the thread can still influence what the agent looks up for you, which is one more reason nothing that changes things runs without your approval.
- **What it finds goes into its reply to the whole group.** Ask only for what you're happy for the group to see.
- The connector's sign-in is kept by Cloud Tag, encrypted. It never enters the agent's sandbox or the group's vault.

## If something goes wrong

Cloud Tag makes each call to your connector at most once, even if it has to retry delivering what came back to the agent. If it can't tell whether a call that changes something went through, for example because your service timed out, it doesn't try again: it stops and says so in the thread. Check the service before asking again, so the change isn't made twice.

## Turn it off

On **Your connectors**, untick an organization to stop its agents using the connector, or **Remove** the connector to revoke it everywhere.

## Differences from Claude Tag

- Allowing a connector in a thread covers only its read-only tools, for a day. Every other call asks you, by email, with exactly what it will do.
- There's no hold for sensitive content in results yet.
- The agent reaches personal connectors through Cloud Tag's own tools, one call at a time, rather than as native connectors.