Smartsheet Server MCP Server

Smartsheet Server becomes available to MCP clients through the smartsheet server mcp server. A Model Context Protocol server.

What Smartsheet Server does

A Model Context Protocol (MCP) server that provides seamless integration with Smartsheet, enabling automated operations on Smartsheet documents through a standardized interface. This server bridges the gap between AI-powered automation tools and Smartsheet's powerful collaboration platform.

The Smartsheet MCP Server is designed to facilitate intelligent interactions with Smartsheet, providing a robust set of tools for document management, data operations, and column customization. It serves as a critical component in automated workflows, enabling AI systems to programmatically interact with Smartsheet data while maintaining data integrity and enforcing business rules.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Auto — number configurations
• System — managed columns
• Multi — select picklist values
• Formula — based columns
• Case — sensitive and whole word options
• Column — specific search capabilities
• Returns — - Matched row IDs (primary result)
• TEXT_NUMBER — DATE
• CHECKBOX — PICKLIST
• CONTACT_LIST — Configurable options:
• Type — specific comparisons (text, dates, numbers)
• Features — - Automatic batch processing (3 rows per batch for optimal performance)
• Token — aware content chunking for large text
• Real — time status updates

Installing the smartsheet server mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 6 environment variables: PYTHON_PATH, SMARTSHEET_API_KEY, AZURE_OPENAI_API_KEY, AZURE_OPENAI_API_BASE, AZURE_OPENAI_API_VERSION, AZURE_OPENAI_DEPLOYMENT. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js and npm - Conda (for environment management) - Smartsheet API access token - Azure OpenAI API access (for batch analysis features)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Smartsheet Server sits in that group, and the shape of its toolset — Auto, System, Multi among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Smartsheet Server.
• Maintained by terilios, written in Python.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the smartsheet server mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.