Skip to main content
These steps use the Kiro CLI.

​
Set up the connection

1

Create the MCP config file

Kiro reads MCP servers from ~/.kiro/settings/mcp.json. If the file doesn’t exist yet, create it:
2

Add the SuprSend MCP server

Open the file:
Add:
~/.kiro/settings/mcp.json
Save the file.
3

Sign in with your SuprSend account

Start kiro-cli and run:
Kiro prints a sign-in URL in the chat. Copy it into your browser and sign in with your SuprSend account. The agent gets the same permissions your role has in the SuprSend dashboard.
4

Restart Kiro and verify

Quit kiro-cli and start it again so it loads the SuprSend tools. Then ask:
Kiro answers with your SuprSend workspaces.

​
Pin a workspace and restrict tools

By default, Kiro 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 url in your config:
  • 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:
Don’t add send tools to Kiro’s autoApprove list, so Kiro asks before each one. 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.”
Quit kiro-cli and start it again. Kiro loads the tools only after a restart.

Tool list

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

Prompt cheatsheet

Ready-to-use prompts to get started fast.