# MCP connector sign-in and access control

People sign in with your organisation's own identity provider, through TechWolf, and the AI tool receives a one-hour token for that one person, never a password or a shared key. Every call checks that person's access again, so they see exactly what they can see in the TechWolf Console.

## Sign-in

![A sequence across three zones: your organisation (your sign-in and the person), the AI vendor (the AI tool) and TechWolf in your region (sign-in and the MCP connector). 1, the person adds the connector to the AI tool. 2, the AI tool registers itself with TechWolf sign-in. 3, the person opens sign-in. 4, a consent page names the AI tool and the person confirms. 5, TechWolf sends the person to your sign-in for SSO and MFA and learns who signed in. 6, TechWolf checks the same organisation, the TechWolf Agent role and that the connector is on. 7, the AI tool gets a one-time code. 8, it sends the code with its PKCE proof and gets a one-hour token and a refresh token. 9, it makes tool calls with the token.](/static/image/sign-in.0f212538.png)

The person's password never reaches the AI tool or TechWolf's connector. The one-time code from step 7 is useless without the PKCE proof that only the AI tool that started the sign-in holds.

**Standard.** OAuth 2.1 authorisation code flow. PKCE (S256) is required, and return addresses must match exactly. AI tools register themselves with Dynamic Client Registration as public clients. AI tools that cannot register themselves get a client set up by TechWolf.

**Consent.** Before sign-in, a TechWolf page names the AI tool as it registered itself and asks the person to confirm. The page is tied to the person's browser session, checks the request's origin and cannot be embedded in another site. The name alone does not prove which tool is asking, so a person should continue only if they started the connection themselves.

**Identity.** The person signs in through your organisation's sign-in connection, the same one the TechWolf Console uses, so your identity provider's MFA, password and session rules apply. The identity must belong to the organisation that owns the TechWolf tenant.

**Every call is made as one person.** The connector accepts only tokens issued to a signed-in person. It accepts no shared or service credentials.

## Tokens

| Token | Lifetime | What it allows |
| --- | --- | --- |
| Access token | 1 hour | Calls to the connector, for one person in one organisation. Signed with a key per region and valid only for the connector. |
| Refresh token | Renews while in use; expires after 7 days without use | A new access token, after the person's role and the organisation switch are checked again. |

**What the AI tool can read in the token.** Tokens are signed, not encrypted. The AI tool can read the person's email address, user ID and organisation ID from them. It never receives the person's password or their identity provider's token.

**How access ends.**

- Removing a person's **TechWolf Agent** role in the Console stops their next call and their next renewal.
- Switching the connector off for the organisation stops every call at once.
- After 7 days without use, the person must sign in again.

## Access checks

Through the connector, a person sees exactly what they can see in the TechWolf Console, checked again on every call. When a check cannot be completed, access is refused.

| Check | What it enforces | When |
| --- | --- | --- |
| Organisation switch | The connector is switched on for your organisation | At consent, sign-in, renewal and every call |
| TechWolf Agent role | The person may use TechWolf agents at all | At sign-in, renewal and every call |
| Data category | The person has access to the kind of data the tool reads: Skill Supply, Skill Demand or Tasks on Jobs. Market search needs the role alone. | Every call |
| Data roles | Only the rows the person may see in the Console, for example their own part of the organisation | Every read, enforced by TechWolf's data service |

**How fast changes take effect.** A removed role stops the person's next call. Changed data roles apply within 60 seconds. Lists held in memory expire within 5 minutes.

## Tenant isolation

- The organisation is fixed in the signed token. It must match the address the call arrives on.
- Every request to TechWolf's data service is scoped to that one organisation.
- Each region signs tokens with its own keys, so a token from one region is not accepted in another.
- Lists held in memory and rate-limit counters are kept per person and per organisation.

## TechWolf staff

Staff can use the connector only on TechWolf's own demo organisations, or from TechWolf's secured virtual desktop in your region. They still need a Console account and the **TechWolf Agent** role in your organisation, and their calls are recorded like everyone else's.

## Related pages

- [MCP connector security](/agent-integrations/mcp-connector/security)
- [MCP connector controls and shared responsibility](/agent-integrations/mcp-connector/security/controls-and-shared-responsibility)