The SmartSuite MCP Server connects AI assistants such as Claude and ChatGPT to your workspace. Once connected, you ask questions about your data in plain language, update records and build tables and automations from a conversation.
SmartSuite hosts the server, so there is nothing to install and no API key to manage.
Example: a risk lead asks Claude, "Which Tier 1 vendors have an open finding older than 30 days?" Claude reads the Vendors and Findings tables through the MCP Server and lists them. With Read & Write access, she then asks it to set each one's Review Status to Escalated.
Plan Availability | All plan types. |
Permissions | Any member can connect. What the assistant can do is limited by that member's permissions and by the workspace's MCP Access setting. |
Platform | Web |
Related Reading |
What is MCP?
MCP, the Model Context Protocol, is an open standard that lets AI assistants connect to other systems and work in them. It is the difference between pasting data into a chat and letting the assistant reach SmartSuite itself.
Ways to connect
If you use. | How to connect. |
Claude (claude.ai, Cowork, the desktop app). | Add SmartSuite as a custom connector with the server URL. See Connect SmartSuite to Claude. |
ChatGPT. | Add SmartSuite as a custom MCP server in a Business, Enterprise or Edu workspace. See Connect SmartSuite to ChatGPT. |
Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, Amazon Quick or another MCP tool. | Add the server URL. See Connect SmartSuite to Other AI Tools. |
The server URL is https://app.smartsuite.com/v1/mcp. If SmartSuite already shows in your assistant's list, select it.
Teams that must run the server themselves can use SmartSuite's open-source Local MCP Server instead.
What it can do
Explore your workspace: list solutions and tables, and read each table's structure, including every field's type, options and help text.
Work with records: search, filter, sort and page through records; create, update and delete them; make bulk changes.
Work around a record: read and write comments, upload files and check My Work.
Build: create solutions, tables, fields, select options and record forms, and arrange the record layout into sections and tabs.
Views and forms: read and edit both, and submit a form.
Automations: read automations as triggers, steps, loops and branches; write new ones; read run history; retry a run.
Note: The assistant acts as you. It sees what you see and does only what you can do. Every change goes into the record's activity history under both your name and the assistant's.
Using it
Once connected, ask. There is no special syntax. Name the solution or table when you know it.
Questions about your data:
How many open risks are there in the GRC solution, grouped by severity?
Which vendors have a contract renewal in the next 60 days and no review scheduled?
Updates:
Set Status to Complete on every control test in the Q3 Testing table that has all checklist items done.
Take the notes in this email and create a record in the Vendor Assessments table.
Building:
Create a table called Incidents with a title, severity as a single select, reported date, assignee and a link to the Vendors table.
Build a form for the Incidents table with the reporter's name, description, severity and an attachment field.
Audits of what you have:
List every automation in this solution and tell me which ones are off.
Walk through the fields in the Contracts table and flag any with no help text.
Tips for good results
Name things exactly. "The Vendors table in the Vendor Risk solution" beats "my vendors."
Preview large changes. Ask "show me what you would change before you change it" on bulk updates and deletes.
Ask for a check. "List what you changed" after a bulk update gives you a quick audit.
Build in a sandbox first. Try structural changes in a test workspace or solution.
Point at an example. "Make one like the Escalation automation" works better than a description.
Controlling access
Two settings decide what an assistant can do, and the stricter one wins:
The workspace's MCP Access, set by an Administrator: Disabled, Read-Only (the default) or Read & Write.
Your connection, chosen when you sign in: which workspaces, and read only or read and write.
Lowering MCP Access takes effect on every connection within about a minute. EU-hosted workspaces are served from the EU, so their MCP traffic stays there. See Choosing Your Data Region.
Frequently asked questions
Do I need to install anything?
Do I need to install anything?
No. SmartSuite hosts the server. You only sign in.
Can the assistant see data I cannot see?
Can the assistant see data I cannot see?
No. It acts as you and is bound by your role and permissions.
Can my Administrator see what the assistant did?
Can my Administrator see what the assistant did?
Yes. Every change appears in the record's activity history under both your name and the assistant's.
Can I connect more than one workspace?
Can I connect more than one workspace?
Yes. Choose them when you sign in, and change the choice later.
I can read but not write. Why?
I can read but not write. Why?
Your connection was set to read only, or the workspace's MCP Access is Read-Only or Disabled. The stricter setting applies.
Can an Administrator undo what an assistant changed?
Can an Administrator undo what an assistant changed?
No. Changes made through MCP cannot be rolled back as a set. Correct a value by editing the record.
Need more help? Ask the SmartSuite Community, where builders, administrators and the SmartSuite team answer questions about building on SmartSuite. For your account, billing or data, select the chat button in the lower-right corner of SmartSuite to reach support.
Last verified 1 Nov 2026.