Skip to main content

MCP connector for Claude Team & Enterprise admins

How a Claude workspace admin adds Focal as an org-wide connector, so teammates can connect with one click instead of each adding it individually.

Overview

If your team is on a Claude Team or Enterprise plan, a Claude workspace admin can add Focal as a connector once, for the whole workspace. Teammates then just click Connect and sign in with their own Focal account — no one else needs to know the connector URL or set anything up themselves.

This is the recommended way to roll out the Focal MCP connector to a team. If you're an individual on a Claude Pro or Max plan, see Connect Focal to Claude instead.

Before you start

  • You need admin or owner access on your Claude workspace (Team or Enterprise plan).

  • You need an admin role in your Focal organization to reach the connector setup page.

  • The MCP connector must be enabled for your Focal organization. If you don't see MCP connector under Organization settings, reach out to your Focal contact to have it turned on.

Step 1: Get your connector URL from Focal

  1. In Focal, open Settings → Organization → MCP connector.

  2. Copy the Connector URL shown on the page (it looks like https://api.focal.inc/mcp).

Step 2: Add Focal in Claude's admin settings

  1. In Claude, open Admin settings → Connectors.

  2. Click Add connector, name it Focal, and paste the connector URL from Step 1.

Claude registers itself with Focal automatically the first time someone connects — there's no client ID or secret to copy anywhere.

Step 3: Teammates connect individually

Once you've added Focal at the workspace level, teammates will see it listed under Settings → Connectors in Claude. Each person:

  1. Clicks Connect next to Focal.

  2. Signs in with their own Focal account.

  3. Optionally restricts the connection to specific spaces.

Important: adding the connector at the workspace level does not grant blanket access to your organization's data. Each teammate's connection is personal — Claude only ever sees what that individual's own Focal account can already access, scoped further by whatever spaces they choose during setup. There's no way for a workspace-level connector to see more than the sum of what its individual connections are authorized for.

Who can't connect

Guest accounts in Focal can't use the MCP connector, even if Focal is available in the Claude workspace. Guests will see an error explaining this if they try to connect — ask an organization admin to upgrade them to a full member first.

Managing connections

Focal doesn't have a way to see or revoke connections on Claude's side of things — that's managed entirely from Claude's admin settings (removing the connector) or by each teammate individually. On the Focal side, each user can see and revoke their own active connection from their personal Settings → MCP page at any time; this immediately cuts off that connection without affecting anyone else's.

See also

Did this answer your question?