How to Use the Conduit MCP in Cline

Q: Can Cline build a monitoring UI for my Conduit pipelines?

Yes, Cline can query your pipeline status using getrunstatus and write a custom dashboard component in your project to display live execution metrics.

Q: How does Cline check which database connectors Conduit supports?

Cline calls listavailabledestinations and listavailablesources to see what systems you can connect. It then uses this list to write your integration setup scripts.

Q: Can I manually force a pipeline run using this setup?

Yes. You can tell Cline to start a run, and it will use triggerworkflow to initiate the sync immediately and report back when it finishes.

Build dashboards and manage Conduit data pipelines autonomously using Cline in VS Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Conduit MCP to Cline

Create your Vinkius account to connect Conduit to Cline and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Conduit with Cline

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Automate Conduit deployments with this MCP Server

The `list_workflows` tool gives Cline a direct view of your active Conduit pipelines so it can build local interfaces matching your live setup. Cline scans the active IDs and starts drafting your frontend code immediately. By calling `get_workflow`, Cline fetches the exact source and destination details of your pipeline. It uses this schema data to write type-safe React components that display your real-time data flows.

Trigger and debug pipelines directly from the sidebar

The `trigger_workflow` tool allows Cline to kick off a pipeline run directly from your VS Code sidebar using this MCP Server. When you ask Cline to test a new database connection, it runs the workflow and monitors the outcome. Cline uses `get_run_status` to track the state of the triggered workflow. If the run fails, Cline reads the error payload, edits your config files, and tries again.

Audit integration nodes and run histories

The `list_connections` tool lets Cline inspect your current source and destination nodes to ensure your local environment matches production. Cline flags mismatched endpoints before you deploy. When troubleshooting, Cline calls `list_workflow_runs` to pull execution logs. It parses these timestamps to build a local timeline of your pipeline's performance.

Setup guide

Set up Conduit MCP in Cline

Prerequisites

VS Code with Cline extension installed
Active Vinkius subscription with a valid endpoint token

1

Open Cline MCP settings

Click the Cline icon in the VS Code sidebar to open the Cline panel. Then click the MCP Servers icon (server stack) at the top-right corner of the panel.
2

Add a remote server

Click "Remote Servers" at the top, then click "Add Remote MCP". In the Name field, type conduit-mcp. In the URL field, paste your Vinkius endpoint: https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp. Get your token from cloud.vinkius.com.
3

Enable the server

After saving, the server appears in the Cline MCP panel. Toggle the switch to enable it. The status indicator turns green when the connection is live.
4

Start using tools

Return to the Cline chat and ask: "Check my latest Conduit refund status." Cline will discover the available tools and request your approval before invoking each one — giving you full control over every action.

Cline MCP Settings

{
  "mcpServers": {
    "conduit-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Conduit. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Conduit now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Conduit MCP in Cline

Click the MCP Servers icon in the Cline sidebar and use the Remote Servers tab to paste your Vinkius URL. You can also edit `cline_mcp_settings.json` manually.

Yes, Cline can query your pipeline status using `get_run_status` and write a custom dashboard component in your project to display live execution metrics.

Cline calls `list_available_destinations` and `list_available_sources` to see what systems you can connect. It then uses this list to write your integration setup scripts.

Yes. You can tell Cline to start a run, and it will use `trigger_workflow` to initiate the sync immediately and report back when it finishes.

Vinkius isolates the connection through its secure MCP sandbox, meaning Cline only accesses pipeline configurations, connection states, and workflow execution logs. Your raw database passwords and actual payloads are never exposed to the LLM.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript