Skip to main content

Quickstart

The fastest way to see what the SmartSuite MCP Server can do is to build something from scratch. You don't need a data model or a single Table set up by hand. Describe what you want to track, hand your assistant whatever raw material you already have, and it builds a structured Solution for you.

Start from scratch: turn a messy spreadsheet into a working Solution​

Imagine you're putting together a Solution to track the organizations your team works with, your contacts at each one, and the projects you're running for them. All you have is one flat tracking spreadsheet, with duplicate companies, inconsistent dates and a few gaps.

What you'll need​

  • A SmartSuite account.
  • A Workspace where assistants are allowed to make changes. A sandbox Workspace is ideal.
  • An MCP-compatible AI tool. This guide uses Claude, but any supported client works.

Step 1: Allow changes in a sandbox Workspace​

Every Workspace starts with MCP Access set to Read-Only, so assistants can read but not build. A Workspace Administrator changes this:

  1. Open Workspace Administration.
  2. Go to AI Control Center → MCP Access and click Edit.
  3. Choose Read & Write and click Save Configuration.
tip

Use a sandbox or build Workspace for this, not production. "Write" covers structure as well as Record values: in Read & Write, an assistant can create Tables, Fields, Views, Forms and Automations. See Controls for recommended setups.

Step 2: Connect SmartSuite to your AI tool​

Add the SmartSuite connector in your AI tool and sign in to SmartSuite. When asked, choose:

  • Read and write access, so the assistant can build.
  • Only your sandbox Workspace. One Workspace is plenty for this walkthrough.

See the connection guides for client-specific steps.

Step 3: Describe what you want and hand over your mess​

Describe what you want to track in plain language, and attach or paste the raw material you already have. You don't need to know anything about Fields or Field types.

Here's what I want to keep track of: the organizations we work with, our contacts at each one, and the projects we're running for them, with statuses, owners and due dates.

And here's what I've got: our team's tracking spreadsheet, attached. Fair warning, it's messy: duplicate companies, inconsistent dates and a few gaps.

Using SmartSuite, propose a Solution in my sandbox Workspace. Once I approve it, build it and load my data in.

Step 4: Review the structure before anything is built​

Your assistant proposes the Tables, Fields and how they link, for example three linked Tables for Organizations, Contacts and Projects, with Status, Date and Assigned To Fields. Refine it in conversation until it's right.

Ask for a dry run if you want to see exactly what the assistant would create. The tools that change structure can report what they would do without doing it.

Step 5: Let it build the Solution and load your data​

Once you approve, the assistant creates the Solution, Tables, Fields and links, then reads your spreadsheet and writes clean, de-duplicated, linked Records rather than a flat copy. Ask it to flag rows it couldn't resolve instead of guessing.

You've got a working Solution​

From here you can:

  • Ask questions across your data. "Which projects are due in the next two weeks, and who's our contact for each?"
  • Keep feeding it new material to add Records over time.
  • Keep building. Add Views, a dashboard, an intake Form or an Automation.
  • Check the work. Ask the assistant to review the Solution against SmartSuite's design standards.

When you're happy with it, share the Solution with your team in SmartSuite. Teammates can use it directly, or connect their own AI tools to it. If the Workspace should go back to read-only for assistants, an Administrator can change MCP Access at any time, and existing connections follow within about a minute.