MCP Server for AI tools to access and manipulate SmartSuite data
planned
D
Dave Hyndman
There should be a pre-built MCP server so AI tools (ChatGPT, Claude, etc) can more natively access and edit SmartSuite data.
Here is an MCP server for Airtable: https://github.com/domdomegg/airtable-mcp-server
Autopilot
Merged in a post:
Native MCP connector for Claude / AI assistants
A
Alfonso Díaz Smith
Please build an official MCP (Model Context Protocol) connector for SmartSuite, similar to what Notion, Airtable, Attio, and Asana already offer. This would let users connect SmartSuite directly to Claude, ChatGPT, and any other MCP-compatible AI assistant.
Why this matters:
- AI assistants are becoming the primary interface for power users designing complex workspaces. Without a native connector, we either operate blind or rely on community-maintained connectors that may break.
- Concrete use cases I run into every week: verify exact field slugs before building a Zap, query record counts to validate a migration, design schemas conversationally with AI, debug automations by reading records directly.
- Competing platforms already have this. Notion's MCP launched 2024, Airtable shortly after, Attio in early 2025. SmartSuite is at risk of being skipped over by AI-first teams when evaluating no-code platforms.
What the connector should support at minimum:
- List solutions, tables, and field schemas (read)
- Query records with filters
- Create, update, and delete records
- Bulk operations for migrations
- Read automation status and logs
Writing this from a real workspace mid-migration where the lack of a native connector is creating friction. Happy to share use cases in more detail if useful.
Autopilot
Merged in a post:
Native MCP connector for Claude / AI assistants
A
Alfonso Díaz Smith
Please build an official MCP (Model Context Protocol) connector for SmartSuite, similar to what Notion, Airtable, Attio, and Asana already offer. This would let users connect SmartSuite directly to Claude, ChatGPT, and any other MCP-compatible AI assistant.
Why this matters:
- AI assistants are becoming the primary interface for power users designing complex workspaces. Without a native connector, we either operate blind or rely on community-maintained connectors that may break.
- Concrete use cases I run into every week: verify exact field slugs before building a Zap, query record counts to validate a migration, design schemas conversationally with AI, debug automations by reading records directly.
- Competing platforms already have this. Notion's MCP launched 2024, Airtable shortly after, Attio in early 2025. SmartSuite is at risk of being skipped over by AI-first teams when evaluating no-code platforms.
What the connector should support at minimum:
- List solutions, tables, and field schemas (read)
- Query records with filters
- Create, update, and delete records
- Bulk operations for migrations
- Read automation status and logs
Writing this from a real workspace mid-migration where the lack of a native connector is creating friction. Happy to share use cases in more detail if useful.
S
Sheldon Garnett
Was actually coming here to suggest this.
Isaac Duran
Great to hear! I've been using Federico's smartsuite MCP and it works wonders. high suggest to link up with him as he's got a working build :)
F
Federico Gonzalez
Finally!!
Peter Novosel
marked this post as
planned
We are planning an official SmartSuite Model Context Protocol server that allows AI systems, including Claude Desktop, Cursor, Cline, ChatGPT-compatible MCP clients, and future SmartSuite AI agents, to securely inspect SmartSuite workspace structure and read or write SmartSuite data through governed tools.
Goals
The SmartSuite MCP Server should:
- Allow AI clients to discover SmartSuite account, solution, application, field, view, and record structure.
- Provide governed read access to SmartSuite records.
- Provide governed write access for creating, updating, deleting, and commenting on records.
- Support schema-level operations, including application and field creation or updates where permitted.
- Respect SmartSuite permissions, roles, field visibility, and audit controls.
- Support enterprise deployment modes, including local, hosted, and private network operation.
- Provide safe defaults so AI clients cannot accidentally perform destructive actions without explicit user approval.
- Serve as a foundational integration layer for SmartSuite Agents, SmartSuite Assistants, and external AI tooling.
Benjamin ~ Identify Solutions
Peter Novosel is there a timeline on this?
Tristan Scifo
Essential
A
Amanda Peers
Are there any updates on implementing this in 2026?
F
Federico Gonzalez
I've created an MCP for SmartSuite you can check it here: https://github.com/Grupo-AFAL/smartsuite_mcp_server
L
Leo Dusseja
Seems not having it as stoneage platform
Load More
→