SmartSuite MCP Server
A locally-hosted MCP server enabling AI agents to securely interact with SmartSuite data, with configurable access modes and audit logging.
README
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.
Installation
Option 1: npm (global)
npm install -g @smartsuite/mcp-server
Option 2: npx (no install)
npx @smartsuite/mcp-server
Option 3: Docker
docker pull smartsuite/mcp-server:latest
Quick 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-mcp
Quick 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:latest
Access modes
| Mode | Read | Create/Update | Delete | Schema writes |
|---|---|---|---|---|
readonly |
✅ | ❌ | ❌ | ❌ |
readwrite |
✅ | ✅ | opt-in | opt-in |
admin |
✅ | ✅ | opt-in | opt-in |
Set with SMARTSUITE_MCP_MODE. Default is readonly.
Configuration
Required
| Variable | Description |
|---|---|
SMARTSUITE_ACCOUNT_ID |
Your SmartSuite account ID |
SMARTSUITE_API_KEY |
Your SmartSuite API key |
Optional
| Variable | Default | Description |
|---|---|---|
SMARTSUITE_BASE_URL |
https://app.smartsuite.com/api/v1 |
API base URL |
SMARTSUITE_MCP_MODE |
readonly |
Access mode: readonly, readwrite, admin |
SMARTSUITE_MAX_RECORDS |
100 |
Hard cap for list/query tools |
SMARTSUITE_MAX_BATCH_WRITES |
25 |
Max records per batch update |
SMARTSUITE_ENABLE_DELETE |
false |
Enable delete tools |
SMARTSUITE_ENABLE_SCHEMA_WRITE |
false |
Enable schema write tools |
SMARTSUITE_ENABLE_SMARTDOC_WRITE |
false |
Enable SmartDoc append tools |
SMARTSUITE_ALLOWED_SOLUTIONS |
(all) | Comma-separated solution IDs to allow |
SMARTSUITE_ALLOWED_APPLICATIONS |
(all) | Comma-separated application IDs to allow |
SMARTSUITE_DENIED_APPLICATIONS |
(none) | Comma-separated application IDs to block |
SMARTSUITE_LOG_LEVEL |
info |
Log level: debug, info, warn, error |
SMARTSUITE_LOG_FILE |
stderr | Path to write logs (default: stderr) |
SMARTSUITE_REQUEST_TIMEOUT_MS |
30000 |
HTTP request timeout in milliseconds |
SMARTSUITE_RETRY_COUNT |
2 |
Number of retries for rate limits and transient errors |
SCHEMA_CACHE_TTL_MS |
300000 |
Application schema cache TTL (5 min) |
Tool list
Discovery & Schema
| Tool | Description |
|---|---|
smartsuite_diagnostics |
Validate configuration and connectivity |
smartsuite_list_solutions |
List accessible SmartSuite solutions |
smartsuite_get_solution |
Get solution details |
smartsuite_list_applications |
List applications; pass solutionId to filter to one solution |
smartsuite_describe_application |
Full application schema with field slugs and options |
smartsuite_list_fields |
List fields for an application |
smartsuite_describe_field |
Detailed field metadata including choice options |
Records
| Tool | Mode | Description |
|---|---|---|
smartsuite_list_records |
readonly | List records with optional sort and field projection; pass ids to fetch specific records by ID |
smartsuite_get_record |
readonly | Get a record by ID |
smartsuite_search_records |
readonly | Text search across specified fields |
smartsuite_query_records |
readonly | Structured filter query |
smartsuite_create_record |
readwrite | Create a new record |
smartsuite_update_record |
readwrite | Update one record |
smartsuite_update_records |
readwrite | Batch update with dry-run support |
smartsuite_delete_records |
readwrite + enable_delete | Delete records with confirmation |
Comments
| Tool | Mode | Description |
|---|---|---|
smartsuite_list_comments |
readonly | List comments on a record |
smartsuite_create_comment |
readwrite | Add a comment to a record |
Views
| Tool | Description |
|---|---|
smartsuite_list_views |
List views for an application |
smartsuite_describe_view |
View metadata: fields, filters, sorts |
SmartDocs
| Tool | Mode | Description |
|---|---|---|
smartsuite_get_smartdoc_content |
readonly | Read a SmartDoc field as plain text and raw value |
smartsuite_append_smartdoc_content |
readwrite + enable_smartdoc_write | Append markdown to a SmartDoc field |
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.
- 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
Project 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
tools/
registry.ts Tool definitions (names, schemas, annotations)
context.ts Shared tool context type
diagnostics.ts
solutions.ts
applications.ts
fields.ts
records.read.ts
records.write.ts
comments.ts
views.ts
smartdocs.ts
types/
config.ts Config interface
smartsuite.ts SmartSuite API types
utils/
audit.ts Audit log writer
pagination.ts Cursor encode/decode
redaction.ts Secret redaction
retry.ts Exponential backoff retry
safeJson.ts Safe JSON stringify
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.