Skip to main content

Cline

Open the Cline panel → settings (gear icon) → MCP Servers → Edit. Save and restart the panel.

Hosted (recommended)

{
  "mcpServers": {
    "talonic": {
      "url": "https://mcp.talonic.com/mcp",
      "headers": {
        "Authorization": "Bearer tlnc_your_key_here"
      }
    }
  }
}

Local (npx)

{
  "mcpServers": {
    "talonic": {
      "command": "npx",
      "args": ["-y", "@talonic/mcp@latest"],
      "env": {
        "TALONIC_API_KEY": "tlnc_your_key_here"
      }
    }
  }
}

Cline runs inside VS Code and communicates with MCP servers over stdio (local) or HTTP (hosted). After adding the config, the Talonic tools become available in Cline's autonomous agent mode, where it can chain multiple tool calls without manual approval for each step.

Cline's auto-approval feature works well with Talonic workflows. For example, the agent can search for documents, filter results, and extract data from the top match in a single turn. Configure Cline's auto-approve settings to control which Talonic tools run without confirmation.

Because Cline operates within VS Code, it has access to your workspace file system. The file_path parameter on talonic_extract and talonic_to_markdown can reference any file in your open workspace, making it straightforward to process documents alongside code.

Example: multi-step workflow with auto-approval

Cline auto-approve config for Talonic read-only tools
// In Cline settings → Auto-approve, allow these tools:
// - talonic_list_schemas (read-only, no cost)
// - talonic_search (read-only, low cost)
// - talonic_get_document (read-only, no cost)
//
// Keep these requiring approval:
// - talonic_extract (costs credits)
// - talonic_save_schema (writes to workspace)

// Agent workflow in a single turn:
// 1. talonic_search → finds matching documents (auto-approved)
// 2. talonic_get_document → checks metadata (auto-approved)
// 3. talonic_extract → extracts data (user approves)

Cline's strength with Talonic is its autonomous agent mode combined with granular auto-approval. By auto-approving read-only tools like talonic_search, talonic_list_schemas, and talonic_get_document, the agent can explore the workspace freely and only pause for user confirmation on credit-consuming operations like talonic_extract. This creates a smooth experience where the agent does the discovery work autonomously and only asks for permission when it matters.

For development teams using VS Code with Cline, the MCP server integrates naturally into code review workflows. A developer can ask the agent to extract data from a specification document, compare it against the implementation in the codebase, and flag any mismatches — all within the same VS Code window. The agent chains talonic_extract with file reads from the workspace to perform this cross-referencing automatically.

If Cline shows the MCP server as disconnected after a VS Code update, re-open the Cline panel settings and verify the config is still present. Some VS Code updates can reset extension state.

Frequently asked questions

How do I add Talonic MCP to Cline?+
Open the Cline panel settings, go to MCP Servers, click Edit, and add the Talonic config entry.
Does Cline support auto-approval for Talonic tools?+
Yes. Configure Cline's auto-approve settings to allow specific Talonic tools to run without manual confirmation, enabling multi-step workflows in a single turn.
Can Cline access local files for Talonic extraction?+
Yes. Cline runs inside VS Code and has access to your workspace file system, so you can use file_path to reference any file in the open workspace.
Which Talonic tools should I auto-approve in Cline?+
Auto-approve read-only tools like talonic_list_schemas, talonic_search, and talonic_get_document. Keep talonic_extract and talonic_save_schema requiring manual approval since they consume credits or write to your workspace.

Related

Continue
Cursor