Taktile MCP server

Learn how to connect AI assistants such as Claude, Cursor, and Cortex Code to your Taktile Workspace through the Taktile MCP server.

The Taktile MCP server lets AI assistants work in your Taktile Workspace through the Model Context Protocol (MCP). Once connected, an assistant such as Claude, Cursor, or Cortex Code can build and test Decision Flows, work with cases, set up connections, and more, on your behalf.

The MCP server uses the same tools as Taktile AI (sign-in necessary). Anything Taktile AI can do in the Taktile app, your own MCP client can do too.

Find your MCP URL

Each Workspace has its own MCP server with its own URL. An MCP client connected to one Workspace cannot read or change anything in another Workspace. To work in several Workspaces, add one MCP server per Workspace to your client.

To find the MCP URL of your Workspace, follow these steps:

1. Open the Workspace in Taktile.
2. Go to Settings.
3. In the side menu, click MCP URL.
4. Click Copy to copy the URL, then click Done.

The URL has the format https://<your-workspace-domain>/mcp.

Connect your MCP client

The Taktile MCP server is a remote MCP server that uses the Streamable HTTP transport and OAuth sign-in. To add it to your client, follow the steps for your client below. In every example, replace <MCP URL> with the URL you copied from Settings.

Claude Code

1. Add the server from your terminal:

   claude mcp add --transport http taktile <MCP URL>

2. Start Claude Code and run /mcp.
3. Select taktile, then select Authenticate.
4. Sign in to Taktile in the browser window that opens and click Authorize.

To make the server available in all your projects, add --scope user to the command.

Claude and Claude Cowork

Custom connectors work in Claude Cowork, Claude Desktop, and Claude on the web.

1. In Claude, go to Settings > Connectors.
2. Click Add custom connector.
3. Enter a name, for example Taktile, and paste your MCP URL as the remote MCP server URL.
4. Click Add, then click Connect.
5. Sign in to Taktile and click Authorize.

On Claude Team and Enterprise plans, an organization owner must add the custom connector first. Each member then connects it with their own Taktile account. For details, see the Claude documentation on custom connectors.

Cursor

1. Open ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
2. Add the Taktile server:

   {
     "mcpServers": {
       "taktile": {
         "url": "<MCP URL>"
       }
     }
   }

3. Open Cursor Settings > Tools & MCP and sign in to the taktile server when prompted.
4. Sign in to Taktile in the browser window that opens and click Authorize.

If sign-in fails with redirect_uri must be https or a loopback address, Cursor sent a cursor:// callback that Taktile doesn't accept. To connect anyway, route the connection through mcp-remote, which requires Node.js:

{
  "mcpServers": {
    "taktile": {
      "command": "npx",
      "args": ["-y", "mcp-remote@0.15.2", "<MCP URL>"]
    }
  }
}

mcp-remote opens the Taktile sign-in page in your browser and receives the callback on a local port.

Cortex Code

1. Add the server from your terminal:

   cortex mcp add taktile <MCP URL> --transport http

2. When Cortex Code prompts you to authenticate, sign in to Taktile in the browser window that opens and click Authorize.

Cortex Code stores the server in ~/.snowflake/cortex/mcp.json. For details, see the Snowflake documentation on Cortex Code MCP support.

Other clients

Any MCP client that supports remote servers with OAuth can connect. Configure the client with these settings:

The client discovers the Taktile sign-in page from the server. You don't need to configure an authorization server.

Authentication and permissions

The MCP server always acts as you. When you connect a client, you sign in with your Taktile account and approve access on the Authorize access screen. The client then works in that Workspace with your roles and permissions, so it can't do anything that you can't do in the Taktile app.

Access tokens expire after 15 minutes, and your client refreshes them in the background. Audited tool calls appear in the audit log under your name, marked as Acting through the MCP server.

Available tools

The MCP server offers the same tools as Taktile AI, grouped into these categories:

The tool set grows regularly. Your client always lists the tools that are currently available.

Send feedback

The MCP server includes a tool for sending feedback to Taktile. To report a tool that fails or behaves unexpectedly, a missing capability, or other product feedback, ask your assistant to submit feedback. The assistant can name the tool the feedback is about, so the report reaches the team that owns it.