The Assignar MCP connector lets Claude Desktop read your Assignar data, so you can ask questions in plain language instead of running reports. MCP (Model Context Protocol) is the standard Claude uses to connect to other systems. You need API access on your Assignar account and someone with the Manage API Access permission to copy your company's Client ID and Client Secret from the Assignar dashboard.
What the Assignar MCP connector can do
Once connected, you can ask Claude things like:
"How many hours did Josh Harris work last week?"
"Show me this week's allocations."
"Create a PDF of all the Site Diaries for Harbour City Council last week."
"What's the status of order 30?"
The Assignar MCP connector is read-only: it fetches data from Assignar but cannot change or delete anything. It can read the same data as the Assignar Public API. For the full list, see the Assignar API documentation at apidocs.assignar.com.
The connector works in Claude Desktop on Mac and Windows. It runs through a small bridge on your own computer, so it doesn't work in Claude on the web or in the Claude mobile apps.
Before you connect Claude to Assignar
API access must be on for your company. On the Assignar dashboard, check for Settings > API Access in the left menu. If it isn't there, contact your Assignar Customer Success Manager: API access is an add-on they can switch on.
Know your region. Use
auif your Assignar account is hosted in Australia or New Zealand, orusif it's hosted in the United States or Canada. If you're not sure, ask your Customer Success Manager.
Connect Claude Desktop to Assignar
To connect Claude Desktop to your Assignar data:
Copy your Assignar credentials. On the Assignar dashboard, go to Settings > API Access. Click the copy icon in Client ID, then in Client Secret, and paste both somewhere safe. See How do I create API credentials on the dashboard?. Keep the Client Secret private: never share it, post it in a ticket or show it in a screenshot.
Install Node.js. Go to nodejs.org and download the installer marked LTS for your computer (
.pkgfor Mac,.msifor Windows). Run it with the default options. To check it worked, open Terminal (Mac) or PowerShell (Windows), typenode --versionand press Enter. You should seev20or higher.Open the Claude Desktop config file. In Claude Desktop, go to Settings > Developer > Edit Config. This opens the folder that holds the file. Open
claude_desktop_config.jsonin a plain text editor (TextEdit on Mac, Notepad on Windows).Add the Assignar connection. If the file is empty or contains only
{}, replace everything with the block below. If it already lists other MCP servers, add only the"assignar"block inside the existing"mcpServers"section, with a comma between it and the server before it. Don't replace the file, or your other servers disconnect.{ "mcpServers": { "assignar": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.assignar.com/api/mcp", "--header", "X-Assignar-Client-Id:YOUR_CLIENT_ID", "--header", "X-Assignar-Client-Secret:YOUR_CLIENT_SECRET", "--header", "X-Assignar-Region:YOUR_REGION" ] } } }Replace the placeholders. Replace
YOUR_CLIENT_IDandYOUR_CLIENT_SECRETwith the values from step 1, andYOUR_REGIONwithauorus. Keep the quote marks. Save the file.Restart Claude Desktop. Quit it fully: on Mac press Cmd + Q; on Windows right-click the Claude icon in the system tray and choose Quit (closing the window only hides it). Then open Claude Desktop again.
Check the connection. The Assignar tools appear under the Search and tools control below the prompt box. The first launch can take up to a minute while the connector downloads a small component. Try "show me this week's allocations".
Why isn't the Assignar MCP connector working?
These are the common problems with the Assignar MCP connector in Claude Desktop, and their fixes.
No Assignar tools appear. Quit Claude Desktop fully (Cmd + Q on Mac, Quit from the system tray on Windows) and open it again. On a first set-up, wait a minute for the download.
Claude Desktop shows an error when it starts. The config file almost always has a JSON mistake, usually a missing comma or bracket. Paste the file into a JSON validator to find it.
Your other MCP servers disappeared. The config file was replaced instead of added to. Add your other servers back inside the same
"mcpServers"section, separated by commas."npx" command not found. Node.js isn't installed or isn't on your computer's PATH. Reinstall the LTS version from nodejs.org, open a new terminal and run
node --versionagain.Authentication errors, or the tools return no data. Check, in this order: the region (
auorus) matches where your account is hosted, which is the most common cause; the Client ID and Client Secret were copied in full with no spaces; and Settings > API Access still appears on the Assignar dashboard.
Regenerating the Client Secret breaks the MCP connector
Your company has one Client ID and Client Secret for the Assignar API. If someone clicks Regenerate on Settings > API Access on the Assignar dashboard, the old secret stops working everywhere, including in Claude Desktop and any other integration that uses it. Check what else uses the credentials before you regenerate, then update claude_desktop_config.json with the new secret and restart Claude Desktop.
Get help with the Assignar MCP connector
Contact Assignar Support with the region you're using and the error message Claude Desktop shows. Never include your Client Secret.
