MCP Server
The Tiny Command MCP server lets you run your workspace straight from your AI chat. Connect Claude Desktop, Cursor, or any host that speaks the Model Context Protocol, describe what you want, and Tiny Command builds it and operates it for you.
It is hosted at https://mcp.tinycommand.com/v1 and authenticated with a workspace API key you generate yourself.
The Model Context Protocol is an open standard that lets AI hosts call external tools. The Tiny Command MCP server exposes your workspace as a set of journey-shaped tools, so your AI assistant can act inside Tiny Command on your behalf.
Three things you can do
Tiny Command exposes 14 tools grouped into three journeys:
- Build: describe a system ("a lead form, a table to store entries, a Slack follow-up") and get a working preview to approve before anything saves.
- Operate: query and update your tables, trigger published workflows, send from a connected Gmail or Slack, run an agent, or enrich a contact.
- Discover: ask what assets you already have and what your workspace is set up to do.
Generate a key, paste one config block, run your first command.
All 14 tools with inputs, outputs, and examples.
Keys, bearer auth, and per-key permission scopes.
How your data is protected and what leaves your workspace.
How it works
- You generate a scoped API key in the platform.
- You paste a single config block into your AI host.
- You tell your AI what you want; it picks the right Tiny Command tools and runs them, asking for your confirmation before any action that changes data.
Every action runs as you, inside your workspace, respecting the same permissions you have in the web app, and every call is recorded in an audit log you can read yourself.