Delegated access (AI hosts)

Interactive AI assistants and other MCP hosts can connect to Filemark as a signed-in user rather than as a server integration.

Connection flow#

Point the host at https://api.filemark.ca/mcp. A host that supports interactive OAuth needs no further configuration: its first call returns 401 with a pointer to the protected-resource metadata, which names the authorization server, and the host takes it from there:

1. It registers itself (RFC 7591 dynamic client registration at /oauth2/register) as a public client: no client secret, PKCE required. The scopes it declares at registration are its ceiling; scopes Filemark does not publish are dropped rather than refused, and a later authorization asking for more is narrowed to them.
2. It sends the user to /oauth2/authorize with a PKCE S256 challenge and an RFC 8707 resource, either https://api.filemark.ca/mcp or https://api.filemark.ca. Both are required. The user signs in, reviews the application name and requested scopes, and approves or denies. A scope Filemark does not publish is refused here with invalid_scope.
3. On approval the host exchanges its code at /oauth2/token for an access token and a refresh token. The same resource must be sent on every token and refresh request for the grant; a different one is invalid_target. It becomes the token's audience, so a token minted for /mcp works only on the MCP server.

Scopes and visibility#

Every MCP connection needs the mcp scope plus the domain scopes for the tools it will call; see scopes. The consent page lists each requested scope with a plain-language description before the user approves, and the host gets exactly the scopes approved.

Any member of the workspace can approve a request for themselves; no firm-level permission is needed. A delegated token sees exactly the clients its user can see in Filemark, and follows any later change to that user's client assignments or role on its next request.

Token lifetimes#

Consent must be completed within 10 minutes of the redirect, and the authorization code must be redeemed within 60 seconds and only once. Access tokens last up to 60 minutes. Refresh tokens rotate on every use and are single-use: presenting one twice revokes the whole chain. A chain lasts 90 days from the original approval and rotation does not extend it, so a long-lived connection re-authorizes at least quarterly.

Revocation#

To see or withdraw access, sign in at app.filemark.ca, open Developer, and revoke the application under delegated access. Each user sees and revokes their own delegations; workspace owners, and admins who hold Manage developer API, see and can revoke every member's. Revoking takes effect on the application's next request: the token it holds stops working, its refresh token stops working, and any authorization it had not yet redeemed is cancelled, so reconnecting requires a fresh approval. A user who leaves the workspace is treated the same way.