SmartSuite MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SmartSuite MCP Serverlist my SmartSuite solutions"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SmartSuite MCP Server
A locally-hosted Model Context Protocol (MCP) server that gives AI coding agents and desktop assistants governed, auditable access to SmartSuite data.
Works with Claude Desktop, Claude Code, Cursor, Cline, and any other MCP-compatible client.
What this is
The SmartSuite MCP server runs on your machine and communicates with your MCP client over stdio. It proxies requests to the SmartSuite REST API using your account credentials. The server enforces access modes, validates inputs, redacts secrets from logs, and writes local audit logs for all write operations.
Related MCP server: gov-mcp
Installation
Option 1: Claude Desktop extension (.mcpb)
Download the latest smartsuite-mcp-server-*.mcpb from the Releases page, then double-click to install in Claude Desktop. You'll be prompted for your account ID and API key. No Node.js required.
Option 2: npm (global)
npm install -g @smartsuite/mcp-serverOption 3: npx (no install)
npx @smartsuite/mcp-serverOption 4: Docker
docker pull smartsuite/mcp-server:latestQuick start: Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"smartsuite": {
"type": "stdio",
"command": "smartsuite-mcp",
"args": [],
"env": {
"SMARTSUITE_ACCOUNT_ID": "your-account-id",
"SMARTSUITE_API_KEY": "your-api-key",
"SMARTSUITE_BASE_URL": "https://app.smartsuite.com/api/v1",
"SMARTSUITE_MCP_MODE": "readwrite"
}
}
}
}Restart Claude Desktop. You should see the SmartSuite tools in the connector panel.
Quick start: Claude Code
claude mcp add smartsuite \
--env SMARTSUITE_ACCOUNT_ID=your-account-id \
--env SMARTSUITE_API_KEY=your-api-key \
--env SMARTSUITE_BASE_URL=https://app.smartsuite.com/api/v1 \
--env SMARTSUITE_MCP_MODE=readwrite \
-- smartsuite-mcpQuick start: Docker
docker run --rm -i \
-e SMARTSUITE_ACCOUNT_ID=your-account-id \
-e SMARTSUITE_API_KEY=your-api-key \
-e SMARTSUITE_MCP_MODE=readonly \
smartsuite/mcp-server:latestAccess modes
Mode | Read | Create/Update | Delete | Schema writes |
| ✅ | ❌ | ❌ | ❌ |
| ✅ | ✅ | opt-in | opt-in |
| ✅ | ✅ | opt-in | opt-in |
Set with SMARTSUITE_MCP_MODE. Default is readonly.
Cross-workspace access
A SmartSuite API key can often reach several workspaces. By default this server is locked to the single workspace named in SMARTSUITE_ACCOUNT_ID (the "primary" workspace). Set SMARTSUITE_ENABLE_CROSS_WORKSPACE=true to let the server read from other workspaces the key can access.
When enabled:
A new read-only tool
smartsuite_list_workspaceslists the workspaces you can reach (slug, name, solution count, plan). It's hidden when the flag is off.Read tools gain an optional
workspaceparameter — pass a workspace slug or name to run that single call against a non-primary workspace. Omit it to use the primary.Cross-workspace access is read-only. Writes, updates, and deletes always target the primary workspace only; passing
workspaceto a write tool is rejected, regardless of access mode.Restrict the reachable set with
SMARTSUITE_ALLOWED_WORKSPACES(comma-separated slugs or names). Empty means all workspaces the key can access. The primary is always allowed.
// Example: enable cross-workspace, limited to two workspaces
"env": {
"SMARTSUITE_ENABLE_CROSS_WORKSPACE": "true",
"SMARTSUITE_ALLOWED_WORKSPACES": "s36h7yr5,Reveal Risk"
}// Then, in the client:
smartsuite_list_workspaces() → see what's reachable
smartsuite_list_solutions({ workspace: "Reveal Risk" }) → read another workspace by name
smartsuite_describe_application({ applicationId, workspace: "s36h7yr5" }) → by slugConfiguration
Required
Variable | Description |
| Your SmartSuite account ID |
| Your SmartSuite API key |
Optional
Variable | Default | Description |
|
| API base URL |
|
| Access mode: |
|
| Hard cap for list/query tools |
|
| Max records per batch create/update |
|
| Enable delete tools |
|
| Enable restoring soft-deleted records from the trash |
|
| Enable schema write tools (create/update fields, formulas, forms, and automations) |
| (all) | Comma-separated solution IDs to allow |
| (all) | Comma-separated application IDs to allow |
| (none) | Comma-separated application IDs to block |
|
| Allow read access to other workspaces your API key can reach (see Cross-workspace access) |
| (all) | Comma-separated workspace slugs or names reachable when cross-workspace is enabled; empty allows all accessible workspaces |
|
| Log level: |
| stderr | Path to write logs (default: stderr) |
|
| HTTP request timeout in milliseconds |
|
| Number of retries for rate limits and transient errors |
|
| Application schema cache TTL (5 min) |
|
| Return field context (label, type, help text, linked field) with every record response |
| (cwd) | Base directory for solution-migration project files (mappings/diff/xlsx, under |
Tool list
Discovery & Schema
Tool | Description |
| Validate configuration and connectivity |
| List workspaces your API key can access (only when cross-workspace is enabled) |
| List accessible SmartSuite solutions |
| Get solution details |
| List applications; pass |
| Application schema with field slugs, options, help text, and the record term. Pass |
| readwrite + enable_schema_write |
| List fields for an application, with help text |
| Detailed field metadata: choice options, help text (+ format), linked-record targets and display format, formula expression + return type, record-title template, auto-number config, and native AI field config |
| readwrite + enable_schema_write |
| readwrite + enable_schema_write |
| readwrite + enable_schema_write |
| readwrite + enable_schema_write + enable_delete |
Formulas
Tool | Mode | Description |
| readonly | Review formula fields. Application-wide: every formula with return type, validity, native complexity score + tier, and structural metrics (function count, nesting depth, reference counts). Pass |
| readonly | Validate a formula expression against an application without writing anything. Returns |
| readwrite + enable_schema_write | Create a formula field. Validates the expression first (an invalid formula is never created); dry-run preview unless |
| readwrite + enable_schema_write | Update a formula field's expression, label, and/or return type. Validates first; dry-run preview unless |
Records
Tool | Mode | Description |
| readonly | List records with optional sort and field projection; pass |
| readonly | Get a record by ID |
| readonly | Text search across specified fields |
| readonly | Structured filter query |
| readwrite | Create a new record |
| readwrite | Update one record |
| readwrite | Batch update with dry-run support |
| readwrite + enable_delete | Delete records with confirmation |
Comments
Tool | Mode | Description |
| readonly | List comments on a record |
| readwrite | Add a comment to a record |
Views & Dashboards
Tool | Description |
| List views for an application (grid, kanban, calendar, timeline, gantt, map, chart, form). Pass |
| Full configuration for one view: filters, sort, group-by, visible/collapsed fields, sharing settings. For form views, returns form config (title, submit label, branding, redirect, per-field prefill/help) |
| List dashboards for an application with their tabs |
| Full dashboard config: tabs, branding, style. Pass |
Forms
Tool | Mode | Description |
| readonly | List an application's forms with page/field counts, sharing state, and public URL |
| readonly | Full form structure: settings, sharing, and the page-by-page layout (bound fields + content elements, sections, conditions) |
| readwrite + enable_schema_write | Create a form; validates label + field slugs. Dry-run unless |
| readwrite + enable_schema_write | Update form settings, fields, or full |
| readwrite | Submit a form — creates a record through the form's pipeline. Call without |
Automations
Tool | Description |
| List a solution's automations (id, name, enabled state, trigger, action types). Scoped per solution |
| Full automation config: trigger and all action groups |
| Resolve one step's full schema: a trigger (label, inputs+options, exposed fields, condition fields) or a chosen action (label, integration, inputs). Select an action with |
| Workspace automation run usage and plan: plan category, run limit, used, remaining, percent used, enforced |
| Integration credentials a solution's automations use (Gmail, Slack, Teams, webhooks, …) |
| Members available to a solution (id, name, email, job title, status) |
| Create an automation (trigger + actions). Requires |
| Update an automation (label, trigger, actions, timezone) — applies only provided fields, preserves the rest. Trigger/actions you supply replace wholesale. Requires schema-write |
| Delete an automation. Requires schema-write and |
My Work
Tool | Mode | Description |
| readonly | List the authenticated user's assigned work (comment mentions, checklist items, assigned records). Returns a summary (totals, overdue count, breakdowns by type/priority/solution) plus items. Filter by |
| readwrite | Update a My Work item: mark it resolved/open and/or set or clear its due date |
Record-view layout (sections & tabs)
Edit the sections (labeled field groupings) and tabs on an application's record detail view. A section
groups the fields that follow it (until the next section). When tabs are enabled the record view
renders per-tab layouts, so the section tools require tabId — a tab id, "all" (every tab), or
"top" (the hidden top-level layout) — and refuse a silent top-level write. When tabs are disabled,
tabId is omitted. All require readwrite/admin + SMARTSUITE_ENABLE_SCHEMA_WRITE, and preview
unless confirm:true.
Tool | Description |
| Add a section. Place it after a field with |
| Update a section's |
| Remove a section by slug. Removes only the grouping — fields under it are preserved |
| Add a tab. Enables tabs if off (the first tab mirrors the current layout); optional |
| Update a tab's |
| Remove a tab by id. Fields stay in the top-level layout; removing the last tab disables tabs |
| Move/arrange a field in the layout — reorder it, place it under a section ( |
| Hide ( |
| Add/modify/remove display (visibility) logic on a |
Solution migration (schema diff)
Compare a solution across workspaces and produce a diff package, for promoting lower-environment
changes up to production. Set your primary workspace to production (the migration target) and read
the lower environment via cross-workspace access (SMARTSUITE_ENABLE_CROSS_WORKSPACE). All four are
read-only against SmartSuite — they only write local files under SMARTSUITE_MIGRATION_DIR. The diff
covers tables, fields, views, and forms in full; dashboards are compared at the report-config level
(per-widget contents are not yet diffed).
Tool | Description |
| Match lower→prod solutions by exact name (ids differ across workspaces). Propose, then |
| For a confirmed solution pair, match its tables by name (table ids and slugs both regenerate across workspaces); persists the table-id map |
| Diff schemas (lower→prod). Fields match by slug; cross-table references remapped and system values ignored, so only real changes surface. |
| Render the diff as XLSX (Summary + Detail tabs) alongside the JSON |
SmartDocs
Tool | Mode | Description |
| readonly | Read a SmartDoc field as plain text and raw value |
| readwrite | Append markdown to a SmartDoc field |
Files
Tool | Mode | Description |
| readonly | Resolve a file field handle to a signed CDN download URL |
| readwrite | Upload a local file to a SmartSuite file field |
| readwrite | Move (or copy) attachments from one file field to another — one record ( |
Security model
Credentials never reach the LLM. API key and account ID are loaded from environment variables and never included in tool responses or logs.
Secrets are redacted from all log output.
Access mode is enforced server-side. Write tools return a clear error in
readonlymode.Destructive operations require explicit opt-in (
SMARTSUITE_ENABLE_DELETE=true) and a confirmation argument.Batch writes require dry-run acknowledgement or
confirm=true.Application allowlists and denylists prevent access to sensitive tables.
Cross-workspace access is opt-in and read-only. Disabled by default; when enabled, other workspaces can be read but never written, and can be scoped with
SMARTSUITE_ALLOWED_WORKSPACES.All write operations write a local audit log (tool, account, application, record, timestamp, success/failure). Field values are not logged by default.
See SECURITY.md for the full security model.
Troubleshooting
"config error: Missing required environment variable"
Set SMARTSUITE_ACCOUNT_ID and SMARTSUITE_API_KEY in your MCP client config.
"SmartSuite API error 401" Check that your API key is correct and not expired.
"This operation is blocked in readonly mode"
Set SMARTSUITE_MCP_MODE=readwrite to enable writes.
Tools not appearing in Claude Desktop Restart Claude Desktop after updating the config file.
Logs polluting MCP output
Ensure SMARTSUITE_LOG_FILE is set to a file path, or that no other code writes to stdout. The server only writes JSON-RPC to stdout.
Development
# Install dependencies
npm install
# Type-check
npm run typecheck
# Build
npm run build
# Run tests
npm test
# Bundle single file for Docker/MCPB
npm run bundle
# Build and package the Claude Desktop extension (.mcpb)
npm run pack:mcpb
# Output: mcpb/smartsuite-mcp-server-<version>.mcpbProject structure
src/
index.ts Entry point
server.ts MCP server bootstrap and tool dispatch
config.ts Environment variable loader
logger.ts Structured JSON logger (stderr or file)
errors.ts Error classes and codes
auth.ts SmartSuite auth header builder
smartSuiteClient.ts SmartSuite REST API client with schema cache
workspaces.ts Workspace resolver (slug/name → slug) and allowlist
tools/
registry.ts Tool definitions (names, schemas, annotations)
context.ts Shared tool context type
diagnostics.ts
workspaces.ts
solutions.ts
applications.ts
fields.ts
formulas.ts Formula analysis, validation, and field create/update
forms.ts Form review, create/update, and submit (form-type reports)
mywork.ts My Work — the authenticated user's assigned items
records.read.ts
records.write.ts
files.ts
attachments.ts Move/copy attachments between file fields
comments.ts
views.ts
automations.ts Automation review, usage/limits, and create/update/delete
layout.ts Record-view layout: sections, tabs, field move, hide/show, display logic
migration.ts Solution migration tools (match, diff, export)
smartdocs.ts
migration/
types.ts Migration mapping + diff data model
match.ts Name-matching (solutions, tables)
normalize.ts System-noise strip + cross-reference remap
diff.ts Schema diff engine (field/table/solution classification)
project.ts Per-project mapping/diff file persistence
xlsx.ts Dependency-free XLSX writer
types/
config.ts Config interface
smartsuite.ts SmartSuite API types
utils/
audit.ts Audit log writer
pagination.ts Cursor encode/decode
prosemirror.ts ProseMirror/SmartDoc → plain text
redaction.ts Secret redaction
retry.ts Exponential backoff retry
safeJson.ts Safe JSON stringifyLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SmartSuiteFoundry/smartsuite-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server