Skip to main content

​
Set up the connection

1

Add the SuprSend MCP server

Open ~/.gemini/settings.json. If the file doesn’t exist yet, create it first with touch ~/.gemini/settings.json.
Add:
The field name is httpUrl, not url. Gemini Code Assist reads the same file, so the server works there too.
2

Sign in with your SuprSend account

Start Gemini CLI and run:
Gemini CLI opens your browser. Sign in with your SuprSend account. The agent gets the same permissions your role has in the SuprSend dashboard.
3

Verify the connection

In a Gemini CLI session, ask:
Gemini answers with your SuprSend workspaces.

​
Pin a workspace and restrict tools

By default, Gemini CLI can use every workspace and tool your role allows. To keep it on one workspace, or to give it only the tools a job needs, change httpUrl in your settings:
  • Pin a workspace by adding its slug to the path. The agent then can’t switch to another workspace:
  • Restrict tools with ?tools=, a comma-separated list of tool names or groups:
You can also hide tools locally with Gemini’s includeTools and excludeTools fields. Keep trust off: it skips Gemini’s confirmation before each tool call. See Scope the connection for every URL pattern, and the tool list for every tool.

​
Troubleshooting

Check the workspace slug in the URL. It must match a workspace in your SuprSend account exactly, for example staging, not the workspace’s display name. A slug that doesn’t exist fails with 403 workspace_forbidden. To see your slugs, remove the slug, reconnect, and ask: “List my SuprSend workspaces.”

Tool list

Every tool, grouped by category, with read vs write labels.

Prompt cheatsheet

Ready-to-use prompts to get started fast.