MCP server

The Tines MCP server is a first-party Model Context Protocol endpoint built into your Tines tenant. Connect it to an AI client such as ChatGPT, Codex, Cursor, Claude Code, or Claude Desktop, describe what you want in plain language, and your client uses the same story authoring capabilities as Workbench for Stories in build mode to create and modify stories on your behalf.

When to use this 

Use the Tines MCP server when you want to build or change stories from the tool where you already work. For example:

  • "Add an HTTP action that creates a Jira issue when this webhook fires."

  • "Read the current story and add error handling on the Slack action."

  • "Create a new story that polls CrowdStrike and posts to Teams."

Your client turns that into story authoring operations against your tenant. You stay in the conversation; Tines updates on the storyboard.

This is different from a custom MCP server you build inside Tines.

Tines MCP server vs. custom MCP servers in Tines 

Tines offers two different MCP surfaces. They solve opposite problems.

Use the Tines MCP server when the AI should work inside Tines' editing stories on your behalf from Cursor, Claude Code, or similar.

Use a custom MCP server in Tines when the AI should call your stories' lookups, approvals, internal APIs, or other logic you have already modeled as story actions. See Build an MCP server in Tines for how to create one, link tools, and connect clients.

You can use both: an external client might use the Tines MCP server to author stories and a separate custom MCP server to run your production integrations.

How it works 

  1. You add https://your-tenant.tines.com/mcp to your MCP client.

  2. On first use, the client runs OAuth and you approve access on a consent screen titled Tines MCP server, which lists the story authoring capabilities you are granting.

  3. You tell the client what you want, usually in the context of a specific story.

  4. The client loads authoring guidance for that story, then automatically reads, creates, updates, and validates story contents.

  5. You review the result in Tines. Each tool use is recorded in audit logs as MCP activity.

Authentication uses OAuth only, not API keys.

Opening https://<your-tenant>.tines.com/mcp in a browser shows a setup page with copy-ready configuration snippets for common clients.

Working with a story 

The server exposes Workbench story building capabilities: reading and changing stories, creating and updating actions, validation, running actions where permitted, research and listing helpers, and private template operations when your permissions allow.

Related page 

Was this helpful?