An AI assistant that supports MCP — Claude, ChatGPT, Cursor and others — can search, read and change the records in your WrkLst 10 account for you. It signs in with your WrkLst login and works as you, with exactly your permissions, until you disconnect it.
What the assistant can do
Once connected, the assistant can search across works, contacts, sales, consignments, exhibitions and shipments, list and filter one kind of record, read a record in full, and create, change or delete records — only what you may do yourself, in that one account. Every change is attributed to you in the record's history, like a change you made by hand. If the assistant asks for something your permissions do not allow, the refusal names the permission that is missing.
The assistant also receives WrkLst's working rules: find before acting, read before writing, look up the fields, ask before creating, changing or deleting, and report a refusal instead of retrying.
Connecting an assistant
- Open Settings → API Tokens. Under Connect an AI assistant or other software, copy the AI assistant (MCP) address of your account. No token is needed, and an API token does not open this connection — tokens are for the REST API.
- Add the address to your assistant. Claude Desktop, Claude.ai (as a custom connector), ChatGPT (as a connector) and Cursor take it as the server address; Claude Code takes it with
claude mcp add --transport http wrklst <address>, followed by/mcp. - On first use the assistant opens your usual WrkLst sign-in in the browser — password, emailed code or passkey, and your second factor if you have one. Nothing is skipped.
- WrkLst shows what you are allowing: which assistant, which account, and that it will act as you with your permissions. Allow or deny.
One connection is one account. If you work in several WrkLst accounts, sign the assistant in once per account. The connection renews itself for up to 30 days of use; after that, or after you disconnect it, the assistant asks you to sign in again.
Who may connect one
Whether a user may connect an assistant is a permission of their role: AI assistant access (MCP) under Settings → User Roles. Administrator roles hold it by default; an administrator grants it to other roles there, independently of the API access permission for the REST API. Everything an assistant does — which search, which record — is listed under Settings → Interaction Log in the channel AI assistant (MCP), as you.
Disconnecting
Settings → My Profile → Connected apps lists every assistant you have signed in, per account, with when it was connected and its last sign-in. Disconnect ends the connection at once; you can sign the assistant in again at any time. Resetting your password ends every connection in one go. Signing out of WrkLst in your browser does not — an assistant is not your browser, which is why that page exists.
Settings → My Profile → Connected apps.
AI and your data
Nothing connects by itself: an assistant works in your account only after you have signed it in and allowed it, and only for as long as you keep it connected. This follows WrkLst's stance on AI — no AI runs on your archive in the background, and every use of AI is clearly marked. The assistant itself is a service of its provider, not part of WrkLst: what you ask it to read is handled by that assistant. See Does WrkLst use AI on my data?