Setup
One command. Then just ask.
SuiteAction signs you in and wires Claude Code, Cursor and Codex to the hosted service. Connect Google once, restart your editor, then paste a file link into your prompt.
The customer journey
From account to first action.
- 1Sign in to SuiteActionUse GitHub, then follow the dashboard's single Google connection step.
- 2Connect Google WorkspaceApprove Sheets, Docs and Slides once. The connection can be revoked from Google or your dashboard.
- 3Run the setup commandIt signs the CLI in and configures the supported AI tools it finds on your machine.
- 4Restart your editor and askPaste a Google file link and describe the finished result in plain English.
npx @suiteaction/cli setupNot published yet. SuiteAction opens end of August 2026. Until then this command returns a 404 from npm — you can sign in and look around now, and the waitlist email will tell you the moment it works.
# Signs in and wires every supported editor it finds. $ npx @suiteaction/cli setup ✓ Signed in to SuiteAction Google account NOT connected — connect one before your first request: https://app.suiteaction.dev/#connect ✓ Claude Code wired (./.mcp.json) ✓ Cursor wired (~/.cursor/mcp.json) → Codex command ready to paste Restart your MCP client to pick it up. Then ask: “Build a Q3 forecast in this sheet: <link>”
# Manual Claude Code setup $ claude mcp add suiteaction -- \ npx -y @suiteaction/mcp # Restart Claude Code, then ask: “Make row 11 green in <link>.”
// Written automatically to ~/.cursor/mcp.json { "mcpServers": { "suiteaction": { "command": "npx", "args": ["-y", "@suiteaction/mcp"] } } } // Restart Cursor after saving.
# Manual Codex setup $ codex mcp add suiteaction -- \ npx -y @suiteaction/mcp # Restart Codex, then paste the Google file link.
What gets installed
A small local bridge to the hosted engine.
Your AI talks to SuiteAction's MCP package. The package calls the hosted API, which securely uses your connected Google account to complete the requested action.
CLI
Account setup
Signs you in, stores your API key locally, and configures supported clients.
MCP
AI tool bridge
Exposes SuiteAction's task-oriented actions to Claude, Cursor and Codex.
API
Hosted execution
Runs the engine remotely with tenant-isolated credentials and usage controls.
Your real files
Edits the Sheet, Doc or Slides file you point your assistant toward.
Before you connect
What Google asks you to approve.
The consent screen is explicit because SuiteAction edits real files. You stay in control of the connection.
Which Google permissions are requested?
Google asks for permission to see, edit, create and delete your Sheets, Docs and Slides, plus the narrower per-file Drive permission. All four are required so paste-a-link content editing and Drive-level actions can work predictably rather than leaving you with a half-connected product.
Why are the permissions broad?
Google's narrower per-file permission alone would require a picker every time before your AI could touch a file. The broader content scopes make pasting a file link into Claude, Cursor or Codex possible. SuiteAction uses the connection for the task you request.
Is my Google account safe?
Your Google credential is encrypted while travelling and while stored. SuiteAction uses it for the file and task you request; it does not read your documents for advertising or unrelated analysis. Content edits stay in Google's version history, and you can disconnect at any time.
Can I remove access?
Yes. Disconnect in the SuiteAction dashboard or revoke SuiteAction from your Google account settings at any time. Account deletion also removes your keys and stored Google credential and queues revocation with Google.
Do I need to be a developer?
No. The automatic setup path is designed for ordinary Claude, Cursor and Codex users. The individual tabs show the manual commands for developers who prefer to see exactly what is configured.