Configure Your Portal by Asking an AI Assistant
CollabPortals ships an MCP connector, so an AI assistant like Claude or ChatGPT can read and change your portal configuration when you ask it to, in plain language.
Portal configuration is a lot of small switches: which tables a role sees, which fields it can edit, which records it is allowed near. Finding the right switch is usually slower than deciding what you want.
The MCP connector lets you skip the finding. You describe the change, and your assistant makes it.
What it does
CollabPortals runs a standard MCP server, so it works with any assistant that supports remote connectors, including Claude and ChatGPT. Once it is connected, requests like these do the work:
- "In my Client Portal, hide the Internal Notes field from the Client role."
- "Add a record filter to Projects so each client only sees their own."
- "Show Invoices as a tab inside each Client record instead of its own page."
- "What roles and permissions are set on my Sales portal right now?"
Every change lands in your portal exactly as if you had made it in the dashboard, and you can review it there.
Why it matters
It shortens the loop between deciding something and it being true. Setting up a role across a dozen tables is a long click-through; described out loud it is a sentence.
It is also good for the reverse direction. Asking what a role can currently see is faster than auditing the switches yourself, which makes it a genuinely useful way to check a portal before you share it.
What it will not do
The connector is deliberately narrow, and that is a feature.
- It cannot create or delete portals. Those stay in the dashboard.
- It cannot change the records in your Airtable base. It configures the portal, not your data.
- It cannot upload image files, change how users sign in, or set up a custom domain. It can set your theme colors and point the logo or favicon at an image you already host.
- It only ever acts as you, on portals your own account manages.
Two higher-risk changes need you to confirm them first: switching a table to show every record rather than only each user's own, and removing a role. The assistant asks before doing either.
How it works
The connector is one URL, https://www.collabportals.com/api/mcp, added as a custom connector in your assistant. You sign in to CollabPortals and approve the consent screen once, and it works from then on.
The MCP setup guide has the click path for Claude, which we have tested end to end, plus the full list of what the connector can change.
Who it is for
Anyone configuring more than one portal, or one portal with several roles. It is most useful when you already know what you want the permissions to be and the slow part is applying them, which is the normal state of a client portal or a sales rep portal with different views per person.
Try it on your own base
Connect Airtable, build a portal, and share it. Seven days free, no card needed.
Related guides and examples
Roles: One Portal, A Different View for Each Person
Define roles like Admin, Editor and Viewer from a field in your user table. Each role gets a complete permission set of its own, in the same portal.
FeatureField Permissions Down to the Single Column
Control each Airtable field separately, per role: whether it is visible, whether it appears on the create form, whether it can be edited, and whether it is required.
Use caseClients
Give your clients secure, branded access to their project data in Airtable. No extra seats, no code, no complex setup, just share a link.
GuideConfigure Your Airtable Portal With AI: The CollabPortals MCP Connector
Connect CollabPortals to Claude, ChatGPT, or any AI tool with an MCP connector and set up your Airtable portal by asking. What it does, how to turn it on, and how the permissions work.