Cline Integration Guide

Overview

Cline is a VS Code agent extension that can use tools, read files, run commands, and interact with MCP servers. Cup’n’String governs it as an active agent surface, not just editor extensions.

Support level

Active Proxy & Shielding

What Cup’n’String detects

• VS Code extension-host activity
• Cline configuration patterns where available
• MCP server usage
• Provider endpoints and custom base URLs

What it governs

• Tool calls
• MCP servers
• Provider/API traffic
• Secret exposure
• Local services

Recommended policies

• Require approved model/provider endpoints
• Force MCP through managed proxy
• Block unknown command/tool integrations
• Audit tool calls

Setup outline

1. Verify the Cup’n’String agent is active.
2. In VS Code, install and configure the Cline extension.
3. Update Cline’s settings file to direct model API endpoints and MCP config paths through the local Cup’n’String gateway.

Verification

Deploy a mock MCP server tool under Cline and verify that Cup’n’String captures the invocation payload and parameters in the console logs.

Troubleshooting

If Cline fails to locate local models, verify the proxy config isn’t filtering loopback address resolutions.

Known limitations

Visibility depends on extension configuration and whether custom endpoints bypass managed proxies.