1
Add it to Claude Code
claude mcp add -e "CONDUIT_API_KEY=${CONDUIT_API_KEY}" conduit-0c97 -- npx -y @useconduit/mcpRequired:
CONDUIT_API_KEY+ 1 optionalEnvironment Variables
Set these before running Conduit MCP.
VariableDescriptionRequired
CONDUIT_API_KEYYour Conduit API keyYesCONDUIT_API_URLCustom API endpointNoAvailable Tools (12)
Once configured, Conduit MCP gives your AI agent access to:
conduit_list_streamsList all data streamsconduit_get_schemaGet schema for a stream (columns, types, codecs)conduit_create_streamCreate a new streamconduit_ingestSend events to a streamconduit_list_eventsQuery events with pagination & time range filtersconduit_add_forwardAdd a forwarding destination (HTTP, MQTT, or WebSocket) with auth optionsconduit_stream_statsGet ingestion statistics (event count, rate, latency)conduit_analyze_schemaAnalyze a JSON payload for optimal schemaconduit_feedbackSubmit feedback to the Conduit teamconduit_backfillReplay historical events to forwarding destinationsconduit_backfill_statusCheck backfill job progress or list all jobsconduit_time_rangeGet earliest/latest event timestamps for a streamTry It Out
After setup, try these prompts with your AI agent:
→List all available data streams in my Conduit account.
→Analyze the schema for the 'sensors' stream and show me the latest 10 events.
→Set up a new HTTP forward for the 'logs' stream to my data warehouse endpoint.
→Check the ingestion statistics for the 'user-activity' stream.
→Replay historical events from the last 24 hours for the 'transactions' stream.
Prerequisites & system requirements
- An MCP-compatible client (Claude Code, Cursor, Windsurf, Claude Desktop, or Codex)
- Node.js 18+ with npm/npx installed
CONDUIT_API_KEY— Your Conduit API key
Keep this setup from going cold
Save the docs, env vars, and workflow around Conduit MCP in Conare so Claude Code, Codex, and Cursor remember it next time.