Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Conduit with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Equip your AI agent to observe data streams, manage integration pipelines, and monitor nodes on the Conduit platform.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 8 capabilities

The complete Conduit capability set.

These are the exact actions your AI can choose when you ask it to work with Conduit.

Capability set01 / 02

01-04

4 capabilities in this set.

Part of 8 available through Conduit.

  1. 01

    Get run status

    Returns detailed status, timing, and error information. Retrieve the current status of a specific workflow run

  2. 02

    Get workflow

    Returns source, destination, and current status. Retrieve detailed information about a specific workflow

  3. 03

    List available destinations

    Retrieve available data destination connector types supported by Conduit

  4. 04

    List available sources

    Retrieve available data source connector types supported by Conduit

Capability set02 / 02

05-08

4 capabilities in this set.

Part of 8 available through Conduit.

  1. 05

    List connections

    Retrieve a list of all active source and destination connections

  2. 06

    List workflow runs

    Returns the execution history with status and timestamps for each run. Retrieve the history of runs for a specific workflow

  3. 07

    List workflows

    Use this as a starting point to discover workflow IDs for subsequent operations. Retrieve a list of all data integration workflows in Conduit

  4. 08

    Trigger workflow

    Use list_workflows first to find the workflow ID. Manually trigger a run for a specific workflow

Observed, not estimated

814ms average. Fast in production.

Conduit is checked daily against the live service.

Daily averagePeak 1097ms
Aug 24Today
Fastest day
675ms
Slowest day
1097ms
14-day trend
Improving-12%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 8 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Conduit, so you can see the experience inside your AI.

It does not authenticate your account with Conduit. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Conduit Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_BeW6ubE4lh69UAetvEDl1Ynez7lChM15fiyrtFlY/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Conduit capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "conduit-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_BeW6ubE4lh69UAetvEDl1Ynez7lChM15fiyrtFlY/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Conduit owners ask.

  • 01

    How do I systematically obtain an active API Key targeting the Conduit platform?

    Depending absolutely on how your infrastructure deployed the program (standalone desktop executable, core Docker containerized setups, or external Cloud instance providers), keys are defined at setup. Generally, navigate your hosted interface configurations to visually spot specific 'API section' panels or define standard keys via backend environment base configurations (for Docker setup instances, parameters typically refer natively mapping to 'CONDUIT_API_URL'). Insert keys properly downwards with other core data completely preserving original syntax precisely achieving seamless valid interactive integrations securely effortlessly resolving requirements seamlessly connecting completely natively without technical failures preventing operations running clearly correctly natively actively continuously stably.

  • 02

    Can the text-based conversational integration construct entirely new data mapping pipelines logically?

    For maintaining stability and avoiding potentially flawed or disruptive integration commands inadvertently given through free text models over critical systems, this integration focuses capabilities mostly on analytical monitoring, status reviewing and component checks (observer and reporting methodologies). Direct architectural construction mapping entire data flow pipelines heavily relies on original detailed configurations inside Conduit visually rather than natural language textual generative guesses mitigating potential serious enterprise data leaks implicitly actively safely limiting functions structurally appropriately maintaining steady uncompromised safe connections.

  • 03

    Which connector types can the AI list?

    The integration can list both source and destination connectors configured in your Conduit instance. Use the pipeline inspection capabilities to see which plugins are attached, their configuration parameters, and their current health status.

Explore

More in Developer Tools

Suggestions