Moltiplex

For agents: fetch https://moltiplex.io/docs/setup.json for machine-readable setup (no browser required). MCP clients can discover the hosted server from /.well-known/mcp-server-card/server.json (draft SEP-2127 server card).

Get started

Moltiplex gives your coding agent observability in machine format. Sign up, add to your IDE in one click, and your agent handles the rest.

  1. Sign up and get an API key

    Go to moltiplex.io/signup and create an account. You'll get an API key (starts with sk-otel-).

  2. Add to your IDE (one click)

    After creating your key, the signup page shows one-click install buttons with your key already embedded:

    • Cursor — click “Add to Cursor” to auto-configure via deep link
    • Claude Code — copy the pre-filled command and paste it in your terminal
    • Other MCP tools — use the MCP URL and auth header shown on the page

    Keep your key safe: Add .cursor/mcp.json to .gitignore, or use Cursor's user-level MCP settings so the key stays only on your machine.

  3. Your agent helps with OpenTelemetry

    Type Get Moltiplex.io in your IDE. Your agent checks how your code is instrumented and helps you send OTLP traces to https://ingest.moltiplex.io. If you already send OTel to another backend, you can dual-send a copy — it won't clash.

  4. Ask in plain language

    "Why did checkout slow down?" — your agent calls scan, investigate, and get_traces, then combines the evidence with your code to give you the answer.

Sending traces (reference)

Your agent will help you configure this, but here's the reference if you want to do it manually.

Ingest accepts OTLP/HTTP and OTLP/gRPC. Auth header: x-otel-api-key: <your-api-key> or Authorization: Bearer <your-api-key>.

exporters:
  otlp_http/moltiplex:
    endpoint: https://ingest.moltiplex.io
    headers:
      x-otel-api-key: "${env:MOLTIPLEX_API_KEY}"

service:
  pipelines:
    traces:
      exporters: [..., otlp_http/moltiplex]  # add to existing

The same API key works for both ingest and querying — one key, two uses.

Tools & resources

Moltiplex is consumed through the hosted MCP at https://mcp.moltiplex.io/mcp with Authorization: Bearer <your-api-key>. Your IDE loads the tool catalog via MCP tools/list. Tool names and parameters match what the agent sees when connected.

For a compact catalog or full docs for one tool on demand, the server exposes moltiplex_discover_tools and moltiplex_expand_tool. Machine-readable lists also appear in moltiplex.io/docs/setup.json.

Telemetry & investigation

Default workflow: anomalies → drill-down → trace evidence → optional narrative for the user.

scan · investigate · get_traces · humanize · compare_windows · retry_webhook

Analytics & topology

timeseries_plan · timeseries · service_map · genai_usage · sampling_stats

OpenTelemetry onboarding

moltiplex_get_started · moltiplex_authenticate · moltiplex_get_config · moltiplex_how_to_send_otel · moltiplex_detect_otel · moltiplex_verify_connection

Discovery, skills & utilities

moltiplex_discover_tools · moltiplex_expand_tool · moltiplex_load_skill · version · moltiplex_suggest_tool

Tenant administration

Requires a valid API key (same Bearer token as querying).

create_api_key · list_api_keys · disable_api_key · enable_api_key · delete_api_key · register_cursor_webhook · list_cursor_webhooks · delete_cursor_webhook

Auto-dashboards & registries

Automation can now write dashboard specs and supporting registry state directly to Moltiplex. Dashboard warnings are surfaced inline and are non-blocking unless validation errors are present.

dashboards_validate · dashboards_upsert · dashboards_list · dashboards_get · dashboards_delete · dashboards_render_status

services_upsert · services_list_from_traces · business_impact_upsert_flow · business_impact_list_flows · business_impact_delete_flow

requirements_upsert · requirements_list · requirements_delete · events_post · events_list · events_delete

NFR dashboard (MCP App)

Tool nfr_rag_status evaluates requirements against live telemetry; pair it with the dashboard resource below.

Resources

  • NFR Dashboard — URI ui://moltiplex/nfr-dashboard (text/html;profile=mcp-app). Interactive HTML surfaced via MCP resources/read.

Dashboard console

The web console now includes environment dashboards and API key management in one authenticated surface.

  • Open /console/dashboards to view dashboard list and detail pages with Current and As-of modes.
  • Use top navigation to move between Dashboards and API Keys.
  • Use the Logout action in the header to sign out via Clerk.
  • If historical telemetry is missing for an As-of view, the UI shows Unknown / insufficient data instead of fabricated values.

← Back to moltiplex.io