Skip to main content
All Tines integration capabilities

​
About

This is an MCP connector that gives the Sazabi agent tools from your Tines tenant’s own MCP server. Every Tines tenant hosts one at https://<your-tenant>.tines.com/mcp. Tines authenticates it with OAuth and dynamic client registration, so there is nothing to create in Tines in advance. The connector acts as the Tines user who signs in, with that user’s Tines permissions. Sazabi connects it read-only: tools that create or change stories and actions, or run them, stay blocked. What the agent can do:
  • Read stories, their actions, and how the actions connect
  • Find which stories handle a given alert, webhook, or integration
  • Read action configuration to explain what an automation does

​
Prerequisites

  • A Tines tenant on tines.com where your user can use the MCP server
  • Your tenant’s MCP endpoint: https://<your-tenant>.tines.com/mcp. Opening it in a browser shows Tines’ own setup page. Sazabi accepts only a single <tenant>.tines.com host over https with exactly the /mcp path.

​
Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.
1

​
Open the connector

Find Tines in Settings > MCP connectors.
2

​
Enter your tenant’s endpoint

Paste https://<your-tenant>.tines.com/mcp into the Server URL field.
3

​
Authorize

Start the connection. Sazabi redirects you to your tenant to sign in and approve access on the Tines Stories MCP server screen, then back.

​
Set up with the CLI

You can also connect Tines with the Sazabi CLI (installed and authenticated — see sazabi mcp-connectors reference). Tines authenticates over OAuth, so the CLI opens a browser to complete authorization:
Sazabi uses this connector read-only, so write tools stay blocked even without --read-only; pass --project-id <project> to target a specific project. In --json mode the command prints an authorization URL to open, then polls until the connection completes. Confirm the result with sazabi mcp-connectors list.

​
Verify

Open the connector’s connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to use one of those tools and confirm it runs. If no tools appear, confirm the endpoint is your tenant’s and that your Tines user can use the MCP server.

​
Troubleshooting

“MCP server URL must be…” when connecting — Use exactly https://<your-tenant>.tines.com/mcp: https, one tenant host on tines.com, no port, and no other path (a custom MCP server built in a story lives under /mcp/<id> and is a different connection). No tools discovered — Disconnect and reconnect from Settings > MCP connectors, and check that your Tines user can use the MCP server on that tenant. Connection shows needs attention — The authorization may have expired or been revoked; reconnect from Settings > MCP connectors.

​
Further reading

Agent tools

How the agent uses connector tools.

MCP connectors

Browse the connector catalog.