Most SmartSuite MCP connection problems have one of four causes. The connector is not enabled for your assistant's organization. MCP Access is Disabled or Read-Only for the workspace. Multi-factor authentication is not set up in SmartSuite yet. Or the tool is not using the server URL https://app.smartsuite.com/v1/mcp with OAuth sign-in. Find your symptom in the tables below; each row gives the cause and the fix.
Plan Availability | All plans. |
Permissions | Any Member can connect. What the assistant can do is limited by that Member's own permissions and by the workspace's MCP Access setting, which Workspace Administrators change. |
Platform | Web. The hosted server runs at app.smartsuite.com; the assistant can be on web, desktop or mobile. |
Related Reading |
What do I check first?
The server URL is exactly https://app.smartsuite.com/v1/mcp wherever the tool asks for one. Claude and ChatGPT use their directories instead and need no URL.
You can sign in at app.smartsuite.com in a browser, and if your account uses multi-factor authentication it is already set up there.
The workspace's MCP Access (AI Control Center > MCP Access) is not Disabled, and is Read & Write if you expect the assistant to make changes.
The scope you chose when you connected: which workspaces, and read only or read & write. Read only and specific workspaces are selected by default.
Connecting and signing in
Symptom. | Cause. | What to do. |
SmartSuite does not appear in Claude's connector search. | On a Claude Team or Enterprise plan an Owner adds connectors for the organization. | Ask your Claude Owner to add SmartSuite, or add a custom connector with the server URL. |
SmartSuite does not appear in ChatGPT's Apps. | On a ChatGPT Business, Enterprise or Edu plan a workspace admin enables apps. | Ask your ChatGPT admin to enable SmartSuite from Workspace settings > Apps. |
No browser window opens to sign in. | The tool has no authenticate step for this server, or it does not support OAuth for remote servers. | Look for an authenticate or sign-in option in the tool's MCP settings (Claude Code: run /mcp, select smartsuite; Gemini CLI: /mcp auth smartsuite). If the tool only supports local servers, bridge with mcp-remote. |
Sign-in stops at the multi-factor authentication step. | Multi-factor authentication cannot be set up from the connector sign-in screen. | Set it up in SmartSuite first, then connect again. Five incorrect codes end the sign-in; start again from the tool. |
Sign-in keeps failing through the mcp-remote bridge. | The bridge has stale saved credentials. | Delete the ~/.mcp-auth folder, restart the tool and sign in again. |
The tool reports that the user is not authenticated, or an authorization error, and the SmartSuite tools do not load. | The tool has no valid SmartSuite sign-in for this connection. | Disconnect and reconnect: Claude Customize > Connectors > SmartSuite; ChatGPT Settings > Apps > SmartSuite; other tools from their MCP settings. Complete the browser sign-in and choose the workspaces. If the message returns, contact Support with the tool name and the exact text. |
The tool cannot discover the server's tools or schema. | The URL is not exact, or the sign-in did not complete. | Check the URL character for character, reconnect and finish the sign-in. If it repeats, contact Support with the tool name and the exact text. |
The page after sign-in does not load. | The tool's callback is not completing the OAuth flow. | Try the connection again from the tool. If the tool does not support OAuth for remote servers, use the mcp-remote bridge; otherwise contact Support with the tool name and the exact text. |
Workspaces and permissions
Symptom. | Cause. | What to do. |
A workspace is missing from the list when you connect. | Its MCP Access is Disabled. | Ask a Workspace Administrator to set MCP Access to Read-Only or Read & Write. |
The assistant can read but every change is refused. | Your connection is read only, or the workspace's MCP Access is Read-Only. The stricter setting wins. | Reconnect and choose read & write; if changes are still refused, ask an Administrator about MCP Access. |
An Administrator raised MCP Access to Read & Write, but your connection is still read only. | Raising the setting does not upgrade existing connections. | Reconnect and choose read & write. |
The assistant lost access a minute after it worked. | An Administrator lowered MCP Access to Read-Only or Disabled; that applies to every connection within about a minute. | Ask the Administrator; nobody needs to reconnect when the setting is raised again, but write access needs a new connection. |
You need the assistant in more than one workspace. | Workspaces are chosen at sign-in. | Choose them when you connect, or change the connection later from the tool's connector settings. |
The MCP Access row is not shown in AI Control Center. | MCP Access is on every plan, but the row may not be visible in your workspace yet. | Contact Support through the in-app chat; Support can enable it for your workspace. |
MCP Access did not change what a local server can do. | MCP Access governs the hosted server only. The open-source Local MCP Server authenticates with the Member's API key and follows that key's permissions. | Adjust the Member's role and permissions, or revoke the API key. |
Using the assistant
Symptom. | Cause. | What to do. |
The assistant answers without using SmartSuite. | The SmartSuite connector is switched off in the chat's tools menu, or the prompt did not point at SmartSuite. | Switch SmartSuite on in the tools menu, or name SmartSuite, the solution and the table in your prompt. |
The assistant cannot find a table. | It did not get a specific name, or the connected Member cannot see the table. | Name the solution and the table, and check that you can open it in SmartSuite yourself. |
You need to know what an assistant changed. | Every change through MCP is written to the record's activity history. | Open the record's activity history; the entry carries both the Member's name and the assistant's. |
When should I contact Support?
After the checks above, contact Support through the in-app chat. Give the tool and its plan (for example Claude Team or ChatGPT Business), the workspace name, the exact error text, and whether you use the hosted server or the Local MCP Server. Never paste an API key into the chat.
Frequently asked questions
Do I need an API key for the hosted MCP Server?
Do I need an API key for the hosted MCP Server?
No. You sign in to SmartSuite with your own account, including single sign-on, and choose the workspaces and the access level. Only the open-source Local MCP Server uses an API key.
Can an assistant see data I cannot see?
Can an assistant see data I cannot see?
No. It acts as the Member who connected it and is bound by that Member's role and permissions. MCP Access can narrow that further; it can never widen it.
Can I connect one assistant to several workspaces?
Can I connect one assistant to several workspaces?
Yes. Choose the workspaces when you sign in, and change the selection later from the tool's connector settings. Workspaces with MCP Access set to Disabled do not appear in the list.
Does the MCP Server work for workspaces hosted in the EU?
Does the MCP Server work for workspaces hosted in the EU?
Yes. Workspaces hosted in the European Union are served from their own region, so MCP traffic for an EU workspace stays in the EU.
Can I run the MCP server myself?
Can I run the MCP server myself?
Yes. SmartSuite publishes an open-source Local MCP Server on GitHub that runs on your own machine with your API key. Its toolset differs from the hosted server, and MCP Access does not govern it.
Last verified 24 Oct 2026.