Connect Claude
Hook Claude up to your AssetLab account - claude.ai and Claude Desktop via the remote connector, Claude Code via one command.
All Claude surfaces connect through the AssetLab MCP server at https://mcp.assetlab.ca, and you sign in with your own AssetLab account. No API key is needed: Claude acts as you, with your role and your site access, and anything it creates or changes is recorded under your name.
Before you start
- Your organization needs the Enterprise plan or the REST API add-on.
- Your organization decides who may connect an assistant. Out of the box that is Administrators only; an Administrator can open it to Managers or Staff, or allow, limit or block individual people, under Settings → AI Assistants. Requesters cannot connect an assistant.
claude.ai (web)
- In Claude.ai, open Settings → Customize → Connectors, then select Add and add a custom connector.
- Paste the connector URL:
https://mcp.assetlab.ca - On the AssetLab page that opens, choose Sign in with AssetLab. Sign in if you are not already.
- Check the account, organization and role shown, then choose what Claude can do: View and make changes, or View only. Administrators can also tick Share your team's names and email addresses, so Claude can find people, for example to assign a work order; for other roles it is not offered.
- Select Allow. AssetLab tools appear in your conversations. Try: "List my sites."
Claude Desktop
Same flow as claude.ai: add a custom connector with URL https://mcp.assetlab.ca under Settings → Customize → Connectors (select Add), then sign in with AssetLab and select Allow.
Claude Code
claude mcp add --transport http assetlab https://mcp.assetlab.ca
Claude Code opens the same sign-in in your browser. For unattended scripts, use an API key instead and send it as a header:
claude mcp add --transport http assetlab https://mcp.assetlab.ca --header "Authorization: Bearer al_live_..."
Advanced: local stdio server
For clients that only speak stdio, the npm package runs the server locally:
npx @assetlab/mcp-server
It needs Node.js 20 or later, and two environment variables: ASSETLAB_API_KEY (an API key) and ASSETLAB_API_URL (the API base URL shown in Settings → API Keys). The remote connector is simpler - prefer it unless you have a reason.
Verifying the connection
Ask something harmless and specific: "How many assets do I have, by site?" A correct, current answer confirms the connection. If it does not work:
- If the sign-in page says your organization only allows certain roles, or that assistant access is turned off for your account, ask an Administrator to allow you in Settings → AI Assistants.
- If a call is refused with a message naming your role, the web app would refuse the same action for you. If it says your access is view only, you chose View only when connecting or an Administrator set it; reconnect, or ask them to change it.
- Removing and re-adding the connector runs sign-in again cleanly.
Disconnecting
Open your Profile → Connected assistants and select Disconnect. An Administrator can disconnect anyone's assistant under Settings → AI Assistants. Either takes effect on the assistant's next request. Removing the connector in Claude only tidies Claude's settings; disconnecting in AssetLab is the security action. See Security model.