2 min read
The Loop
How your &tag, controller, and MCP tools work together.
The Loop is the relationship between your &tag, the tools connected to it, and the human who stays in control.
Thanks for your feedback!
Your &tag is the identity and context anchor. The controller and MCP-compatible tools are different surfaces for using that same anchor.
Thanks for your feedback!
The surfaces
| Surface | Role |
|---|---|
| Controller | Mobile App for human surface to manage your &tag, documenting directly, reviewing or managing signals, and approving trust-sensitive moments. |
| MCP | Developer and agent connection surface for letting compatible tools use supported And capabilities with your &tag context. |
| Tools | MCP-compatible clients and agents that can read or write supported identity signals after account authentication. |
You do not need to treat these as separate products. They are different ways to participate in the same loop.
Thanks for your feedback!
How the loop works
- Your account owns an
&tag. - The controller gives you a direct surface for that
&tag. - The MCP connects compatible tools to And after account authentication.
- Identity context created through those surfaces remains tied to your
&tag, so the human can review, manage, and stay in the loop.
Thanks for your feedback!
Thanks for your feedback!
Thanks for your feedback!
Thanks for your feedback!
Why the controller matters
The controller is where the ecosystem stays human-centered. MCP-compatible tools let agents work with your &tag; the controller keeps the human aware, able to approve, and able to manage the identity context those tools create.
Thanks for your feedback!
Where to go next
- Before you start — confirm the account prerequisites.
- Connect your &tag — learn the available connection surfaces.
- MCP developers — connect compatible tools to And.
Thanks for your feedback!
Thanks for your feedback!
Thanks for your feedback!