Connect an AI Client

Info

New in Atfinity 17.

The MCP endpoint of your tenant is https://<your-atfinity-host>/api/1/mcp/. Give the tool that address and it finds the rest on its own. If it reports that it cannot discover the server, ask whoever runs your installation to set PUBLIC_BASE_URL.

Credentials

A tool needs its own OAuth client before anyone can grant it access.

Where self-registration is allowed, the tool creates one on first connection and you never see the credentials. It may register up to five redirect URIs, each using https or http on a loopback address such as http://localhost:53682/callback.

Otherwise create the client under API, on the OAuth Clients tab, with the redirect URI the tool asks for. Copy the client secret while it is shown, since it is not stored and cannot be retrieved afterwards.

Granting access

The tool sends you to Atfinity to sign in, and consent narrows a request to read and change down to reading only.

Access belongs to the person who signs in rather than to the tenant, and someone who may not change the configuration is refused whatever the tool asked for.

How long access lasts

An access token lasts a day, and the tool renews it in the background for as long as it is used at least once every thirty days. A tool idle longer than that asks for consent again, and one in daily use never expires, so revoke it when you are done with it.

Credentials belong to one tenant and are refused on another. A token issued for MCP is refused everywhere except the MCP endpoint, so it cannot become a general API credential.