Connect Hiveflow to Claude for your organization (managed auth)
Admin guide to roll out the Hiveflow connector to a Claude Team or Enterprise organization — OAuth endpoints, credentials, console steps, member sign-in, revocation and security.
This guide is for the Owner or Primary Owner of a Claude Team or Enterprise organization who wants to make Hiveflow available to every member from the admin console, instead of each person adding the connector on their own. For the personal setup (claude.ai, Claude Desktop, Claude Code and the plugin) see Hiveflow in Claude and Claude Code.
Everything below describes what the Hiveflow MCP server supports today. The last section lists what is not available yet and what to ask Hiveflow for.
What the connector accesses
The connector is the hosted MCP server at https://mcp.hiveflow.ai. Once a member connects, Claude can act on their Hiveflow account through these tool groups:
| Area | What Claude can do |
|---|---|
| Flows | List flows with their execution state, inspect nodes and edges, create flows, run one, and activate, pause or stop it. |
| Agents | List agents and what each is doing, read an agent's objective, conversation and audit log, chat with it, and halt or resume agents. |
| Approvals | List the actions flows and agents are waiting on (human in the loop) and approve or reject them. |
| Kanban boards and workers | List boards, read columns and cards, create, move and comment on cards, and see which workers are connected. |
| Apps | Read and write the built-in apps: CRM contacts and tasks, conversations, dashboards and inventory. |
| Data tables | List tables, query rows, create tables, and write, update or delete rows. |
| Organizations and workspaces | List what the member belongs to and scope any operation to one of them. |
| Docs | Read the live API reference, so Claude answers questions about Hiveflow itself. |
Every tool is annotated: read-only tools are marked as such, and tools that change data (running a flow, moving a card, writing rows) are marked as mutating, so Claude asks before acting. Nothing in the connector runs as a service account: each call runs as the member who connected, with that member's organization roles and permissions.
OAuth endpoints
Hiveflow runs its own OAuth 2.1 authorization server on the same host as the MCP endpoint. Claude discovers all of this automatically; the table is here for your records, firewall rules and security review.
| Purpose | URL |
|---|---|
| MCP endpoint (the URL you enter in Claude) | https://mcp.hiveflow.ai |
| Protected resource metadata (RFC 9728) | https://mcp.hiveflow.ai/.well-known/oauth-protected-resource |
| Authorization server metadata (RFC 8414) | https://mcp.hiveflow.ai/.well-known/oauth-authorization-server |
| OpenID discovery (same document) | https://mcp.hiveflow.ai/.well-known/openid-configuration |
| Authorization endpoint | https://mcp.hiveflow.ai/oauth/authorize |
| Token endpoint | https://mcp.hiveflow.ai/oauth/token |
| Dynamic client registration (RFC 7591) | https://mcp.hiveflow.ai/oauth/register |
| UserInfo | https://mcp.hiveflow.ai/oauth/userinfo |
Protocol details the server publishes in its metadata:
- Grant types:
authorization_codeandrefresh_token. - PKCE: required,
S256only. - Client authentication:
none— every client is a public client, so there is never a client secret. - Scopes:
mcp,openid,email,profile. Theopenid/email/profilescopes only expose the member's verified email and name on the UserInfo endpoint; they do not widen what the token can do. What a token can do is decided by the member's Hiveflow roles. - Redirect URIs accepted for Claude:
https://claude.ai/api/mcp/auth_callback(claude.ai, Desktop, mobile, Cowork) and loopbackhttp://localhost/http://127.0.0.1on any port (Claude Code). - Token lifetime: access tokens last 7 days; refresh tokens last 30 days and are rotated on every use. Claude renews silently, so members do not see a sign-in prompt while the refresh token is valid.
If your network restricts outbound traffic from Anthropic, both the MCP endpoint and the OAuth endpoints are on mcp.hiveflow.ai; Anthropic's egress range is published in Anthropic's IP address reference.
How Claude identifies itself (credentials)
When you add the connector, Claude's dialog asks how it should identify itself to Hiveflow's authorization server. Two of the three options work with Hiveflow today:
Register automatically (recommended). Claude registers itself through Dynamic Client Registration the first time it connects, and Hiveflow issues a public client_id on the spot. There is nothing to create or copy. Hiveflow skips the consent screen for Claude's known callback URL, so members only see Hiveflow's sign-in page.
Use your own OAuth client (optional). Hiveflow has no admin screen for OAuth clients, but the registration endpoint is public and returns a stable client_id you can pin in the Claude console. Register one from any terminal:
curl -s -X POST https://mcp.hiveflow.ai/oauth/register \
-H "Content-Type: application/json" \
-d '{
"client_name": "Claude — Acme Corp",
"redirect_uris": ["https://claude.ai/api/mcp/auth_callback"]
}'The response contains "client_id": "mcp_…". Enter that value as the OAuth client ID and leave the client secret blank — Hiveflow only supports public clients, and a secret would be rejected. The client name you choose is what members see if a consent screen is ever shown.
Use Claude's published identity (Client ID Metadata Document) is not supported by Hiveflow yet; choosing it will fail the connection. See What is not available yet.
Add the connector in the Claude admin console
The exact layout of the dialog varies by organization; Anthropic documents it in Add a connector that isn't in the directory. The steps for Hiveflow:
- Go to Organization settings → Connectors (claude.ai/admin-settings/connectors). You need to be an Owner or Primary Owner, or on Enterprise, a custom role that can manage the organization's libraries.
- If Hiveflow appears in the connector directory, add it from there. Otherwise select Add → Custom (choose Web if asked for a type) and enter the name
Hiveflowand the URL:https://mcp.hiveflow.ai - Under Authentication, choose Sign in now (each member authorizes before first use) or Sign in when needed (Claude connects without credentials and prompts the member the first time a tool needs their account). Both work with Hiveflow; the server answers unauthenticated calls with
401and the metadata pointer Claude expects. - Under OAuth client, choose Register automatically, or Use your own OAuth client with the
client_idfrom the previous section and an empty secret. Do not add anything under Request headers: the connector uses per-member OAuth tokens, not a shared API key. - Click Add. The connector now appears for members under Customize → Connectors with the Custom label (or the Hiveflow listing if you added it from the directory).
Authentication settings cannot be edited after the connector is added. To change them, remove the connector and add it again; members then reconnect.
How members sign in
Each member connects with their own Hiveflow account — the connector never shares one identity across the organization.
- The member opens Customize → Connectors, finds Hiveflow and clicks Connect (or, with Sign in when needed, Claude prompts them the first time it reaches a Hiveflow tool).
- Hiveflow's sign-in page opens. They can use Google, GitHub, email and password (followed by the one-time code sent by email, the same second factor as the app) or a personal API key from Profile → API Keys.
- They are sent back to Claude. The Hiveflow tools appear in the chat's tool menu, scoped to the organizations and workspaces their Hiveflow account belongs to.
If a member signs in with an API key that has scopes (read, write, execute), the connector inherits those limits: a key with only read gives Claude a read-only view of Hiveflow, which is a simple way to pilot the connector with a team before allowing actions.
Members need a Hiveflow account that belongs to your Hiveflow organization. Invite them from the organization settings in Hiveflow first (Organizations & workspaces); the connector does not create accounts.
Revoke access
There are two sides to a connection, and either one cuts it:
From Claude
- A member disconnects their own account under Customize → Connectors → Hiveflow → Disconnect.
- An Owner removes the connector for the whole organization under Organization settings → Connectors → Remove. Claude discards every member's tokens.
- Removing a member from the Claude organization removes their access to the connector along with the rest of Claude.
From Hiveflow
- Remove the member from your Hiveflow organization. Their token keeps working for their personal account, but it immediately stops seeing the organization's flows, boards, agents and data, because every call is authorized against current membership and roles.
- Change or reset the member's password. Hiveflow revokes all of that account's connector sessions (access and refresh tokens) when the password changes; the member has to connect again.
- Delete the API key if the member signed in with one. The connector session tied to that key stops being renewable at once.
- Suspend the account. A suspended or deactivated Hiveflow account cannot obtain or refresh connector tokens.
Signing out of the Hiveflow web app does not disconnect Claude; that is deliberate, so assistants a member connected on purpose survive a normal logout.
What is not available yet
Claude's Enterprise Managed Auth ("auto-connect") lets an organization connect its members without a sign-in page: Claude sends Hiveflow's authorization server a signed identity assertion (from your identity provider, such as Okta, or issued by Claude) instead of running the interactive OAuth flow. Anthropic describes the requirements in Enterprise Managed Auth for connectors and the admin side in Auto-connect your organization's apps to Claude.
Hiveflow does not support auto-connect yet. Specifically, the Hiveflow authorization server does not accept the urn:ietf:params:oauth:grant-type:jwt-bearer grant, has no setting to register a trusted issuer URL per organization, and does not advertise support for Claude's Client ID Metadata Document, which Enterprise Managed Auth requires instead of dynamic registration. If you open Managed authorization → Set up on the Hiveflow connector in the Claude console, the connection test will fail.
What you can do today is the standard rollout above: the Owner adds the connector once, and each member signs in with their own Hiveflow account.
If your organization needs auto-connect, write to Hiveflow support and ask for:
- support for Enterprise Managed Auth on
mcp.hiveflow.ai(JWT bearer grant and per-organization trusted issuer), stating whether you need IdP-managed (Okta) or Claude-issued assertions; - an organization setting in Hiveflow where an admin enters the issuer URL that Claude shows during setup;
- the Hiveflow directory listing to be marked as supporting auto-connect.
This page will be updated when that ships.
Security
- OAuth 2.1 with PKCE. Every authorization uses
S256PKCE, single-use authorization codes (10 minutes), one-time refresh tokens rotated on each use, and exact redirect URI matching; non-HTTPS redirects are refused except loopback for Claude Code. - Per-member tokens. A token belongs to one Hiveflow user and carries a marker that restricts it to the MCP endpoint and UserInfo; it cannot be replayed against the Hiveflow REST API or the web app. Nothing a connector does counts as a human session in the app.
- Organization roles respected. Each call is authorized against the member's current organizations, workspaces and role permissions (
view_resources,execute_flows,edit_resources, …). A member who cannot run flows in the app cannot run them from Claude either. - Consent and phishing protection. Hiveflow shows a consent screen naming the client and the host the code is sent to, and only skips it for Claude's and ChatGPT's known callback URLs. Login attempts are rate-limited per IP and per account; password sign-in requires the emailed one-time code.
- Audit trail. Client registrations, authorizations, token issuance and refreshes are written to Hiveflow's audit log.
- No shared secrets. There is no client secret, API key or service account to store on the Claude side. Request-header credentials are not used.
- Real side effects. A flow run from a chat sends the emails or messages it contains and consumes execution credits like any other run. Ask members to keep tool approvals on for mutating tools.
Troubleshooting
"Authorization with the MCP server failed" right after adding the connector. Check that the OAuth client option is Register automatically or a client_id from /oauth/register with an empty secret. Use Claude's published identity is not supported.
A member sees a Hiveflow organization missing. Their Hiveflow account is not a member of it, or the organization is not the active one. Ask Claude to list organizations and scope the request, or invite the member in Hiveflow.
"Account mismatch" in Claude Desktop. The browser is signed in to a different Claude account than the app. Sign out in the browser, sign in with the same account, and reconnect.
Connector shows as disconnected after a month of inactivity. The refresh token expired (30 days). The member clicks Connect again.