Preview
What it is.
One connector setup gives every later Claude conversation 39 workflow blocks and 50+ Slate tools across web research, search analysis, generation, CMS publishing and conditional logic.
The bulk path is the useful one: ask for a sheet, add the URLs, run a workflow across every row and export, and the sheet appears in Slate with nobody opening the interface. Slate is TripleDart's own platform, which is worth knowing before you read our view of it.
What you get.
- 39 workflow blocks and 50+ tools reachable from a conversation
- Workflow creation and execution, including listing what already exists
- Bulk operations through sheets, run across every row
- Brand context readable and updatable, through the same versioning and approval
- A one-time setup, after which every conversation has access
How to set it up.
Open Settings then Connectors in Claude Web or Claude Desktop.
Click Add custom connector and paste the Slate MCP server URL, client ID and client secret from your workspace under MCP Connectors.
Click Connect and confirm the login. This is a one-time setup and every later conversation has access.
Ask Claude to list your Slate workspaces, then name the one to work in.
Start by listing existing workflows before creating one, since something close may already be built.
For bulk work, ask for a sheet, add the URLs, then run a workflow across the rows and export the result.
Pricing Plans
It needs a paid Slate workspace.
Check current pricing on slatehq.com. Checked against the product page in July 2026.
Use cases
A workflow across a sheet
You have a pile of URLs needing the same treatment. Ask for a sheet and add the URLs, then run a workflow across every row, and the exported result lands in Slate without anyone opening the interface.
Building by description
The visual workflow builder has a learning curve you'd rather skip. Describe what the workflow should do in conversation and it gets assembled from the available blocks, after a check that something close doesn't already exist.
Brand context housekeeping
The brand context went stale after a messaging update. Update it through the connector in conversation, and the change moves through the same versioning and approval as an edit made in the interface.
Taking stock before building
Nobody remembers what workflows the team already has. Ask for the list first, and duplicated builds stop before they start.
Best for
Bulk content operations
A sheet of URLs with a workflow run across every row is the job that is painful in any interface and reasonable in a conversation.
Building a workflow without the builder
Describing what you want and having it assembled removes the learning curve on the visual editor.
Keeping brand context current
It is readable and updatable through the connector, with versioning intact, so the context does not go stale.