Connect your whole team from Claude, with no sign-in step
An admin sets this up once. After that, people in your Claude organization reach Server4Agent the moment they need it, with nothing to sign in to or approve, and they stay connected.
Set it up in four steps
You need to be an admin on both sides: an Owner in your Claude organization, and the owner or an admin of your Server4Agent account.
Step 01
Open the setup in Claude
In Claude, go to Organization settings, then Connectors, and select Server4Agent. On the Configuration tab, click Set up next to Managed authorization, then choose Claude-issued under Identity source.
Step 02
Copy the issuer URL
Copy the issuer URL Claude shows you, and leave that page open. The URL is unique to your Claude organization.
Step 03
Paste it into Server4Agent
In Server4Agent, open Team, paste the URL under Automatic sign-in, and click Save. Only the account's owner or an admin can do this.
Step 04
Test it and turn it on
Back in Claude, click Test connection, then Enable and continue, and choose who gets the connector. Those people can now use Server4Agent from Claude without signing in.
Server URL, if Claude does not list Server4Agent yet
https://mcp.server4agent.comAdd it as a custom connector for your organization, then start from step 1.
What this does and does not do
Who it is for
Claude Team and Enterprise organizations. Sign-in issued by Claude is in beta on Claude's side, and is not offered to an organization that signs in to Claude through Okta.
How people are matched
By email address. Each person's Claude email has to match a verified address on your Server4Agent team: the owner, an admin or a member who has accepted an invite. Nobody is created automatically, so invite people first.
What Claude vouches for
That the person is a current member of your Claude organization, and which address they use there. It does not check single sign-on or multi-factor authentication.
Viewers
A viewer does not connect this way. The role only opens the app links shared with them, and every Server4Agent tool is a build tool.
Taking access away
Turning this off, or removing someone from your Server4Agent team, ends their access on their next request. Removing someone only from your Claude organization stops new sign-ins, and the access they already have runs out within the hour, so remove them from both.
Nothing else changes
API keys and personal sign-ins keep working beside this, and only the one account that registered the issuer is reachable, even for someone who belongs to several.
What each message means
Claude's connection test shows the step that failed and what came back. These are the answers Server4Agent gives.
No account has registered this issuer.
The URL is not saved in Server4Agent yet. Save it under Team, in the account you are setting up.
More than one account has registered this issuer.
Issuer URLs are not secret, so another account may have saved yours. Copy the Tenant ID from your Team page into Tenant ID (optional) in Claude's setup, which points the sign-in at your account.
This account has not registered this issuer.
The Tenant ID in Claude's setup names an account that saved a different URL. Check both values against your Team page.
No verified teammate on this account has that email address.
Invite that address to your team and have them accept, or have them confirm their address. Their role has to be owner, admin or member.
Connecting one person rather than a whole team? Follow the ordinary setup instead. Building an MCP server of your own? Here is how to accept Claude as a trusted issuer.