Skip to content

Cline TaScan tascan_project_digest

How to: Cline TaScan tascan_project_digest

client:Cline transport:streamable-http tool:tascan_project_digest

Add TaScan to Cline

  1. 01

    Open ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "tascan-mcp": {
      "url": "https://app.tascan.io/mcp"
    }
  }
}
  1. 02

    Save the file and restart Cline.

  2. 03

    Ask for something tascan_project_digest does. Cline lists the server's tools on connect and calls tascan_project_digest itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that TaScan's identifier in your config matches the one above exactly.

Cline's MCP Servers pane edits this file for you if you would rather not find it. Cline docs

Set these first

TaScan will not start until these are set, so tascan_project_digest never becomes available.

  • TASCAN_API_KEY
  • TASCAN_API_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.