Connect Smartsheet to Cline CLI
Give Cline CLI governed access to Smartsheet’s 61 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Smartsheet to Cline CLI in four steps
Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.
- 1
Approve Smartsheet in Runlayer
Add Smartsheet from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Cline CLI to Runlayer
Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Smartsheet’s 61 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Cline CLI setup guide - 3
Sign in to Smartsheet
An admin adds Smartsheet credentials to Runlayer once. They never sit in the client’s configuration.
- 4
Use Smartsheet from Cline CLI
Smartsheet’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.
Tools
61 Smartsheet tools in Cline CLI
Runlayer policy decides which of these Cline CLI users can call.
Add chart to dashboard
Add a previously created chart to a Smartsheet dashboard as a widget.
Add columns
Adds one or more new columns to the specified sheet.
Add comment
Adds a new comment to an existing discussion.
Add rows
Adds one or more new rows to the specified sheet with optional positioning.
Attach URL
Attaches a URL to a Smartsheet sheet, row, or comment.
Browse folder
Browse all children (nested folders, sheets, reports, dashboards, templates) within a folder.
Browse workspace
Browse all children (folders, sheets, reports, dashboards, templates) within a workspace.
Create chart from data
Build a chart structure from pre-computed data values (bar, line, pie, or stacked bar).
Control
What Runlayer can see and stop in Cline CLI
Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.
Gateway policy (available)
Every Smartsheet call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Cline CLI as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Cline CLI runs it.
Block output after it runs (not available)
Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.
Redact output in place (not available)
Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.
In Cline CLI
- If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
- This covers the Cline CLI, not the Cline extension for VS Code.
Frequently asked questions
Connect more