# Tines

Tines AI Agent actions attach remote MCP servers as tools. Cakewalk's gateway runs Streamable HTTP with OAuth 2.1 and supports Dynamic Client Registration, which matches Tines' MCP support directly. Tines registers the OAuth client automatically during setup and surfaces the gateway's tools in the action.

## Install Method

Configure an MCP server on a Tines AI Agent action. Tools the gateway exposes appear alongside the action's other configured tools (Send to Story, Template, Custom) once the connection completes.

## Step 1: Open an AI Agent action

Open the Tines story where you want Cakewalk tools available. Add or edit an **AI Agent** action.

## Step 2: Attach the Cakewalk Gateway

In the AI Agent action's MCP configuration, add a new remote MCP server with:

* Server URL: `https://mcp-gateway.getcakewalk.io/mcp`
* Transport: Streamable HTTP

Save the configuration.

> Tines' published docs describe the MCP feature (transports, auth, DCR) but do not name the exact UI surface where MCP servers attach. If you do not see an MCP section in the AI Agent action, check the action's tool / connection configuration.

## Step 3: Authenticate

During setup, Tines detects that Cakewalk's gateway supports Dynamic Client Registration and registers an OAuth client automatically. Tines then opens the OAuth consent flow in your browser. Sign in with your Cakewalk account and approve the Connection. Tines stores the resulting credentials on the MCP connection record.

## Verifying It Works

After authentication, Cakewalk's tools appear in the AI Agent action's tool list. The action can invoke them the same way as Send to Story, Template, or Custom tools. In Cakewalk, the Tines card on **My Agents** flips to **Connected** after the first agent call.

## If Tines Falls Back to Manual OAuth

Tines documents a manual OAuth path for MCP servers that do not support DCR. Cakewalk's gateway does support DCR, so this fallback should not engage. If it does, the steps Tines describes are:

1. Create an OAuth application in the third-party platform (Cakewalk).
2. Configure the redirect URI Tines specifies and the required scopes.
3. Copy the Client ID and Client Secret.
4. Create an OAuth credential in Tines using those values.
5. Reference that credential in the MCP connection record.

If you reach this path, contact Cakewalk support. The admin surface for minting an OAuth client in Cakewalk is not yet self-serve, and Cakewalk support can mint one for you.

## Troubleshooting

* **Tines does not recognize the URL as an MCP server:** confirm the URL ends in `/mcp` exactly, with no trailing slash or extra path. Tines runs MCP discovery against the URL's well-known endpoints.
* **OAuth flow does not initiate:** confirm your Tines tenant is on a release with MCP OAuth support. Earlier MCP releases in Tines only offered Bearer / generic header authentication, which Cakewalk's gateway does not accept.
* **Cakewalk tools do not appear after auth:** save the action and reopen. Tines loads MCP tools when the action initializes.

## Learn more

* [AI Agent action — MCP section](https://www.tines.com/docs/actions/types/ai-agent/#mcp) from Tines.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.cakewalk.security/docs/ai-agent-access/connections-and-integrations/agent-platforms/tines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.