Reach connector guide
Use Reach from a compatible AI assistant.
Reach exposes a remote Model Context Protocol connector for contact management and email-marketing work. OAuth keeps each connection bound to the Reach workspace and permissions the user approves.
Setup
Connect with one production URL.
- In your assistant's connector settings, add a remote custom connector using
https://www.studioanchor.app/api/mcp. - Choose Connect. Reach opens its own sign-in and permission screen; Reach never asks you to give your password to the assistant.
- Confirm the workspace name and requested view, edit, and send permissions before selecting Allow connection.
- Return to the assistant and enable Reach for the conversation where you want to use it.
Claude users can add a custom connector from Customize → Connectors. On Team or Enterprise plans, an organization owner may need to enable it before members can connect.
Requirements
What the workspace needs.
- A Studio or Pro Reach workspace is required for connector read and write tools.
- Pro access and the Send permission are required for campaign sends and tools that start or resume sequence email.
- A verified sender and physical mailing address are required before Reach can send campaign email.
- The connecting Reach user must have a workspace role that can grant the requested permissions.
Using tools
Discover identifiers before changing anything.
Start with list or search tools to learn the contact, campaign, sequence, tag, and sender identifiers in the connected workspace. Read tools do not change data. Write tools state what they change in their names and descriptions.
Campaign delivery, contact enrollment, sequence resume, and contact deletion use separate prepare and commit steps. A prepare result does not perform the final action. Review the named record, audience, recipient estimate, and warning before asking for its matching commit action.
If the workspace requires human approval for MCP/API campaign sends, a committed campaign stops at pending_approval. Email is not dispatched until a studio owner separately approves it inside Reach.
Disconnect
Revoke access from Reach or the assistant.
In Reach, open Settings → API & Integrations and disconnect the approved app. Reach revokes that connection's access and refresh tokens. You can also remove or disconnect Reach from the assistant's connector settings.
Disconnecting stops future connector access. It does not undo contact, campaign, tag, or sequence changes that the user already asked Reach to make.
Troubleshooting
Check the boundary first.
- Authorization failed: reconnect, verify the workspace name, and approve at least View access. Ask a workspace owner if your role cannot grant Edit or Send.
- A tool says the plan does not allow it: use a tool available to the connected workspace or have the workspace owner review its Reach plan.
- A sender is missing: configure and verify a sender in Reach Settings, then call the sender-list tool again.
- A confirmation token expired: run the matching prepare tool again and review the new result before committing.
- A campaign is pending approval: no email has been sent; a studio owner must review it in Reach.
Do not send passwords, access tokens, API keys, or full customer exports in a support request. See the StudioAnchor Privacy Policy for data handling and retention details.
Need help connecting Reach?
Email StudioAnchor support with the assistant name, the step that failed, and the Reach workspace name. Do not include credentials or tokens.