Workflow context for AI agents with Smartsheet MCP on AWS
Amazon Web Services Galina Jordanowa ● Covered by 2 sources
Smartsheet now has an MCP server on AWS, so AI agents can update sheets and status from plain English. It plugs into Amazon Quick and Kiro, which means work can move without bouncing between tools.
Based on reporting by Amazon Web Services, Galina Jordanowa — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Smartsheet has turned its project data into something AI agents can actually use. The company launched a generally available Model Context Protocol server on AWS, and it’s built to let assistants read, write, and manage Smartsheet data through one standardized interface.
The pitch is simple enough: less tool-switching, more action on the work that already lives in sheets. More than 40 tools are available for sheets, rows, columns, and automations, so a user can update task status, create rows, or change project structure with natural language instead of clicking around in a dashboard.
AWS is treating that server as the center of two very different workflows. Amazon Quick is aimed at business users, project managers, and operations teams who want to ask questions and build dashboards without code. Kiro is for developers who want Smartsheet context inside their coding flow, where they can pull project specs, track dependencies, and update task status without leaving the IDE.
The example that makes the case best is sprint management. A project manager can ask Amazon Quick which sprint tasks are blocked this week, and the agent can pull the relevant rows and summarize owners and due dates from live Smartsheet data. A developer can do the same sort of thing in Kiro, see open backend tasks inline, and then have a hook mark the row Complete when the fix is committed.
Smartsheet says the server returns structured context such as row relationships, column types, cell history, and comments, which keeps payloads smaller than raw API dumps. That’s meant to improve latency and reduce cost when AI-assisted queries start piling up across a portfolio. The server is available at three regional endpoints, uses Streamable HTTP transport, and supports OAuth 2.0 or a Personal Access Token.
My take — AI-written commentary, not fact-checked reporting
This is the sensible version of agent hype: give the model live work data and keep the permissions where they already are. The industry keeps promising magical coworkers; usually it just delivers a fancier search box with confidence issues. Smartsheet at least seems to understand that boring infrastructure is what makes the agent story less embarrassing.
Read more about this at: Amazon Web Services