Workiom MCP/Plugin

Claude is a great thinking partner, but on its own it cannot see your data. Connect it to Workiom and that changes. Claude can read your lists, create and update records, upload files, and even build small internal apps that run inside your own workspace, all using the access you give it and nothing more.

This guide walks you through the whole setup, from uploading the Workiom plugin to authorizing access with your API key. It takes about five minutes, and you only have to do it once.

What you get once it is connected

• Ask questions about your own data in plain language, such as which clients have not been touched in thirty days
• Have Claude create, update, or clean up records for you instead of doing it row by row
• Let Claude build ready to use pages and mini apps that live inside your Workiom workspace
• Keep everything inside your own account, since Claude works through your API key and your permissions

Watch the walkthrough

If you would rather follow along visually, the interactive walkthrough below shows every click in order. You can step through it at your own pace, and it stays in sync with the written steps further down.

Before you start

You will need three things:

1. A Claude account (any paid plan works)
2. A Workiom account with permission to open Workspace Settings
3. The Workiom plugin file

Download the Workiom plugin

Once you have the file, keep it somewhere easy to find. You will upload it in a moment.

Step 1: Open your Claude settings

Go to claude.ai and sign in.

Click your name at the bottom left of the sidebar, then choose Settings.

Step 2: Go to the Plugins page

In the settings menu, look under the Customize heading and click Plugins.

This is where Claude keeps everything that extends what it can do.

Step 3: Upload the Workiom plugin

At the top right of the Plugins page, click Add, then choose Upload plugin.

A small window opens. Click Browse files, pick the Workiom plugin file you downloaded, then click Upload.

You will see a short warning that uploaded plugins are not reviewed by Anthropic. That is standard for any plugin that does not come from the public directory. This one comes from Workiom, so you are good to continue.

After a moment the plugin appears in your list, named Workiom vibe apps, with the toggle already switched on.

Step 4: Install the Workiom connection

Open the plugin and click the Connectors tab. You will see one entry called workiom with an Install button next to it.

Click Install. A form opens with the connection name and address already filled in for you. Leave everything as it is and click Add.

The connection is now registered, but Claude still needs your permission to use it. That is the next step.

Step 5: Start the authorization

Still on the Connectors tab, you will now see workiom listed with a Custom label and a Connect button. Click Connect.

Claude opens a new tab called Authorize Workiom MCP, with a single field waiting for your API key. Leave that tab open. You are about to go and fetch the key.

Step 6: Create your Workiom API key

Your API key is what tells Workiom that this particular Claude account is allowed to act on your behalf. Here is where to find it:

1. Open Workiom in a separate tab and sign in to the workspace you want Claude to work with
2. In the left sidebar, scroll to the bottom and click Workspace Settings
3. Open the Developer section
4. Switch to the Integrations tab, where your existing API keys are listed
5. Click Create new API key at the top right
6. Give the key a name so you recognize it later, something such as "Claude". The field is optional, but naming it saves confusion once you have more than one
7. Click Copy and save

Two things worth knowing before you close that window:

• The key is shown only once. If you lose it, you cannot look it up again, you simply create a new one
• You can delete the key from this same page at any time, which cuts off access instantly

If you do not see Workspace Settings or the Developer section, your account does not have workspace admin rights. Ask whoever administers your Workiom workspace to either grant you access or create a key for you.

Step 7: Authorize the connection

Go back to the Authorize Workiom MCP tab that Claude opened.

Click the API Key field, paste the key you just copied, then click Authorize.

The page lists exactly what you are granting:

• Read your Workiom data
• Create, update, and delete records
• Upload files on your behalf

Nothing outside your own workspace, and nothing you cannot revoke later.

Step 8: Confirm it worked

Once the page confirms authorization, close that tab and return to Claude. Open the plugin's Connectors tab one more time. The workiom entry should now show as connected, with the Connect button gone.

If it still shows Connect, refresh the settings window. The status sometimes takes a moment to catch up.

Try it out

Start a new chat in Claude and ask something simple to confirm everything is wired up, for example:

"List the applications in my Workiom workspace."

Claude will use the connection and answer with your real data. From there you can go further:

"Show me every record in my Leads list created this month, grouped by source."

"Create a record in my Support Tickets list for the issue I just described."

"Build me a page where my team can submit bug reports straight into my Bug Reports list."

If something does not work

Claude says it cannot find your workspace. Reopen the plugin, check the Connectors tab, and make sure the entry shows as connected rather than showing a Connect button.

Authorization failed. The key was probably copied incompletely, or it has been deleted in Workiom. Create a fresh key and authorize again.

The plugin is not being used in chat. Check that the plugin toggle on the Plugins page is switched on.

You want to cut off access. Delete the API key in Workiom under Workspace Settings, then Developer. Access stops immediately, with no need to touch anything in Claude.

A note on safety

Claude only ever reaches Workiom through the key you created, so it inherits your permissions and nothing more. It cannot see other workspaces, and it cannot see anything you do not have access to yourself. If you ever want to hand the connection to someone else on your team, they create their own key and follow the same steps with their own account.

What comes next

Once the connection is in place, the interesting part is not the setup, it is what you stop doing by hand. Reports you used to build column by column, records you used to fix one at a time, small internal tools you kept postponing because they were not worth a development cycle. All of that becomes a conversation.

If you build something useful, we would love to hear about it.

‍