Skip to main content
Glama

@useconduit/mcp

MCP server for Conduit โ€” connect any AI agent to your data streams.

๐Ÿ“– API Docs ยท ๐ŸŒ Website ยท ๐Ÿ“ฆ npm ยท ๐Ÿ’ป GitHub

Quick Start

Get an API key from platform.usecondu.it/tokens, then add to your AI editor config:

Claude Code / Claude Desktop

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "conduit": {
      "command": "npx",
      "args": ["-y", "@useconduit/mcp"],
      "env": {
        "CONDUIT_API_KEY": "conduit_sk_..."
      }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "conduit": {
      "command": "npx",
      "args": ["-y", "@useconduit/mcp"],
      "env": {
        "CONDUIT_API_KEY": "conduit_sk_..."
      }
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "conduit": {
      "command": "npx",
      "args": ["-y", "@useconduit/mcp"],
      "env": {
        "CONDUIT_API_KEY": "conduit_sk_..."
      }
    }
  }
}

Related MCP server: Open Enterprise AI MCP Server

Environment Variables

Variable

Required

Default

Description

CONDUIT_API_KEY

โœ…

โ€”

Your Conduit API key

CONDUIT_API_URL

โ€”

https://api.usecondu.it

Custom API endpoint

Tools

Tool

Description

conduit_list_streams

List all data streams

conduit_get_schema

Get schema for a stream (columns, types, codecs)

conduit_create_stream

Create a new stream

conduit_ingest

Send events to a stream

conduit_list_events

Query events with pagination & time range filters

conduit_add_forward

Add a forwarding destination (HTTP, MQTT, or WebSocket) with auth options

conduit_stream_stats

Get ingestion statistics (event count, rate, latency)

conduit_analyze_schema

Analyze a JSON payload for optimal schema

conduit_feedback

Submit feedback to the Conduit team

conduit_backfill

Replay historical events to forwarding destinations

conduit_backfill_status

Check backfill job progress or list all jobs

conduit_time_range

Get earliest/latest event timestamps for a stream

Resources

URI

Description

conduit://streams

All streams

conduit://streams/{name}

Stream details + schema

conduit://stats

Platform-wide statistics

API Documentation

Full interactive API docs are available at api.usecondu.it/docs (powered by Scalar).

Key endpoints:

Method

Endpoint

Description

POST

/v1/{tenant}/{stream}

Ingest events (any protocol: HTTP, WebSocket, MQTT)

GET

/api/v1/streams

List streams

GET

/api/v1/streams/{name}

Stream details + schema

GET

/api/v1/streams/{name}/events?from=&to=&limit=

Query events with time range

GET

/api/v1/streams/{name}/stats

Ingestion statistics

GET

/api/v1/streams/{name}/schema-history

Schema evolution history

POST

/api/v1/streams/{name}/forwards

Add forwarding destination

POST

/api/v1/streams/{name}/backfill

Start backfill job

GET

/api/v1/streams/{name}/backfill

List backfill jobs

GET

/api/v1/streams/{name}/time-range

Event time range

POST

/api/v1/tokens

Create API token

GET

/api/v1/account

Account info + usage

Machine-readable API specs:

What is Conduit?

Conduit is the lightweight data layer between your services. Send any JSON โ€” schemas aren't defined, they emerge. And they evolve as your sources do.

  • One endpoint, any protocol โ€” HTTP, WebSocket, MQTT/S on the same path

  • AI-powered schema detection โ€” zero configuration, runs locally (your data never leaves)

  • Real-time forwarding โ€” HTTP webhooks, MQTT brokers, WebSocket endpoints with full auth options

  • Backfill โ€” replay historical events to new destinations

  • Built for agents โ€” MCP-native from day one, feedback loop included

  • European infrastructure ๐Ÿ‡ช๐Ÿ‡บ โ€” all data hosted and processed in the EU, GDPR-compliant by design

How agents use Conduit

Agent: "I see live sensor data flowing in. I'll pipe it to our datawarehouse and add hot storage."

โ–ธ conduit_list_events(stream: "sensors", limit: 1000)
  โ†ณ 1,000 events ยท 18.4 MB raw โ†’ 1.1 MB stored (94% compressed)

โ–ธ conduit_add_forward(stream: "sensors", type: "http", url: "https://dwh.acme.io/ingest")
  โ†ณ Destination added ยท forwarding to datawarehouse

โ–ธ conduit_add_forward(stream: "sensors", type: "mqtt", broker: "mqtt://redis.acme.io", topic: "hot/sensors")
  โ†ณ Destination added ยท 2 destinations active

โ–ธ conduit_backfill(stream: "sensors", from: "2026-02-24", to: "2026-03-02")
  โ†ณ Backfilling 89,929 events from last 7 days

Learn more at usecondu.it

License

MIT

Available Tools

15 tools
conduit_add_forwardC

Add a forwarding destination to a stream. Supports HTTP webhooks, MQTT brokers, and WebSocket endpoints. Events are forwarded in real-time.

Inputs: stream (required), dest_type, url, broker, +7 more.

conduit_analyze_schemaB

Analyze a JSON payload and get the optimal ClickHouse schema with compression codecs

Inputs: payload (required).

conduit_backfillA

Replay historical events from a stream to one or more forwarding destinations. Runs as a background job with progress tracking.

Inputs: stream (required), from (required), to (required), destination_ids.

conduit_backfill_statusB

Check the status of a backfill job โ€” progress, events processed, errors.

Inputs: stream (required), job_id.

conduit_create_streamA

Create a new data stream. Just send a name โ€” schema is auto-detected from the first event.

Inputs: name (required), description.

conduit_create_transformB

Create a new transform for a stream. The code should be a JS function body that receives an event object and returns the transformed event. Available helpers: pick, omit, get, set, flatten, rename, mapValues, mapKeys.

Inputs: stream (required), name (required), code (required).

conduit_feedbackB

Submit feedback to the Conduit team โ€” bugs, feature requests, improvements, or praise

Inputs: category (required), message (required), context.

conduit_get_schemaB

Get the current schema (columns, types, codecs) for a stream

Inputs: stream (required).

conduit_ingestB

Send one or more events (JSON objects) to a stream. Schema is auto-detected and evolves.

Inputs: stream (required), events (required).

conduit_list_eventsB

Query events from a stream with optional pagination and time range filters

Inputs: stream (required), limit, offset, from, +1 more.

conduit_list_streamsB

List all data streams in your Conduit account

Inputs: no named parameters.

conduit_list_transformsB

List all transforms configured for a stream. Transforms are JS functions applied to events before forwarding to destinations.

Inputs: stream (required).

conduit_preview_transformA

Preview a transform by running it against a sample payload without persisting. Returns the transformed output and execution time.

Inputs: stream (required), code (required), payload (required).

conduit_stream_statsB

Get ingestion statistics for a stream (event count, rate, schema version)

Inputs: stream (required).

conduit_time_rangeA

Get the time range and total event count for a stream. Useful before starting a backfill.

Inputs: stream (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelogโ€ฆ

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: adding destinations, analyzing schemas, backfilling data, creating streams/transforms, submitting feedback, getting schemas, ingesting events, listing events/streams/transforms, previewing transforms, getting stats, and checking time ranges. The descriptions reinforce unique functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent 'conduit_verb_noun' pattern (e.g., conduit_add_forward, conduit_analyze_schema), with verbs like add, analyze, backfill, create, get, list, preview, and stream. This uniformity enhances predictability and readability across the toolset.

    Tool Count5/5

    With 15 tools, the set is well-scoped for a data streaming and processing server, covering core operations like ingestion, transformation, forwarding, querying, and management. Each tool serves a specific role without redundancy, fitting the domain's complexity appropriately.

    Completeness5/5

    The toolset provides complete coverage for data streaming workflows: creating and managing streams (create, list, stats), ingesting and querying events (ingest, list_events), transforming data (create_transform, list_transforms, preview_transform), forwarding (add_forward, backfill), and schema handling (analyze_schema, get_schema). No obvious gaps exist, supporting end-to-end agent operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects AI agents and MCP clients to Keboola, enabling storage queries, SQL transformations, job triggers, and more through natural language.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Connects AI coding assistants like Claude Code, Cursor, and Windsurf to enterprise data sources (databases, files, APIs, etc.) via a single binary, with 45+ connector categories and built-in memory tools.
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Connects AI agents to live observability stacks including Sentry, GitHub, Vercel, Better Stack, and Cloudflare, enabling end-to-end incident investigation, deployment correlation, root cause analysis, and regression triage.
      14
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create, validate, and manage agent-powered workflows across team tools, with tools for inspecting schemas, configuring triggers, and reviewing runs and logs. It provides authorized remote access through OAuth without local installation or shared API keys.
      1
      MIT