Koskamo

Dataset Join & Merge MCP

A remote MCP server that allows agents to join two lists of JSON rows on a specified key, supporting operations similar to SQL joins or VLOOKUP functions such as left, inner, full, and anti joins, as well as union operations.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Dataset Join & Merge MCP logo, by Nero LabsCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Nero Labs
MCP endpoint (Streamable HTTP)
https://dataset-join-merge.nerolabs.workers.dev/mcp
Vendor documentation

What its tools do

2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

2 of 2 have a description · 0 of 2 declare behavior hints · 1 of 1 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Join two lists of JSON rows on a key
  • Perform SQL-like joins (left, inner, full, anti)
  • Execute union operations on datasets
  • Retrieve server capabilities

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
nerolabs-dataset-join-merge 0.1.0
MCP protocol negotiated in check
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Call join_rows with leftRows, rightRows and leftKeyFields to join two lists of JSON rows on a shared key (left, inner, right, full, anti joins or union). Call list_capabilities first for every option and the row limits.

Tools

2 advertised

list_capabilities
Advertised by the server during the last successful anonymous check.

Returns every join type, key matching mode, conflict strategy and fan-out mode this server supports, the fields it adds to each row, and the input and output row limits per call. Free, processes no data.

list_capabilities input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
join_rows
Advertised by the server during the last successful anonymous check.

Joins two lists of JSON rows on a shared key, like a SQL join or a spreadsheet VLOOKUP, and returns the combined rows plus a summary: how many rows matched on each side, match rates, and warnings for duplicate keys, rows missing the key and key fields that exist on no row. Use it to enrich a list with fields from a lookup table (left join), keep only the overlap (inner), combine two sources into one table (full), find rows in one list that are missing from the other (leftAnti or rightAnti), or stack two same-shape lists (union). Keys match case-insensitively with whitespace trimmed by default, and the key can have a different name on each side (email on the left, contact_email on the right). Input and output rows are capped per call; a many-to-many join that would exceed the output cap is refused with the predicted row count, never truncated. Call list_capabilities for the exact limits.

join_rows input schema
{
  "type": "object",
  "required": [
    "leftRows",
    "rightRows"
  ],
  "properties": {
    "joinType": {
      "enum": [
        "left",
        "inner",
        "right",
        "full",
        "leftAnti",
        "rightAnti",
        "union"
      ],
      "type": "string",
      "description": "Which rows to keep. left (default): every left row, enriched where a match exists. inner: matched rows only. right: every right row. full: everything from both sides. leftAnti: left rows with no match on the right. rightAnti: right rows with no match on the left. union: stack both lists, no key needed."
    },
    "leftRows": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The LEFT table: the main rows you want to keep or enrich. Each row is a JSON object; keys may differ between rows."
    },
    "rightRows": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "The RIGHT table: the lookup rows to pull matching fields from. Each row is a JSON object."
    },
    "keyMatching": {
      "enum": [
        "normalized",
        "exact"
      ],
      "type": "string",
      "description": "normalized (default): case-insensitive, trimmed, repeated spaces collapsed, 123 matches \"123\". exact: values must be identical."
    },
    "rightFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only copy these fields from the matching right row, like choosing VLOOKUP return columns. Leave out to copy every right field."
    },
    "leftKeyFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The field name(s) on the left rows to match on, for example [\"email\"], or [\"firstName\",\"lastName\"] for a composite key. Required for every joinType except union."
    },
    "rightKeyFields": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "The matching field name(s) on the right rows, in the same order as leftKeyFields, for example [\"contact_email\"]. Leave out when the right rows use the same names as the left."
    },
    "includeJoinInfo": {
      "type": "boolean",
      "description": "On by default: every row gets _joinStatus (\"matched\", \"left_only\", \"right_only\") and _matchCount. Set false for rows with only your own fields."
    },
    "multipleMatches": {
      "enum": [
        "all",
        "first"
      ],
      "type": "string",
      "description": "When one key matches several right rows. all (default): one output row per matching pair, like SQL. first: only the first matching right row, like VLOOKUP, so each left row appears once."
    },
    "onFieldConflict": {
      "enum": [
        "prefixRight",
        "keepLeft",
        "keepRight"
      ],
      "type": "string",
      "description": "When a right field has the same name as a left field. prefixRight (default): keep both, the right one renamed with rightFieldPrefix. keepLeft: ignore the right value. keepRight: overwrite the left value."
    },
    "rightFieldPrefix": {
      "type": "string",
      "description": "Prefix for conflicting right fields when onFieldConflict is prefixRight. Default \"right_\", so price becomes right_price."
    }
  },
  "additionalProperties": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
334 ms
95th percentile latency
334 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 334 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http dataset-join-merge-mcp https://dataset-join-merge.nerolabs.workers.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add dataset-join-merge-mcp --url https://dataset-join-merge.nerolabs.workers.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable dataset-join-merge-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "dataset-join-merge-mcp": {
      "url": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "dataset-join-merge-mcp": {
      "type": "streamableHttp",
      "url": "https://dataset-join-merge.nerolabs.workers.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start dataset-join-merge-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "dataset-join-merge-mcp": {
      "type": "http",
      "url": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http dataset-join-merge-mcp https://dataset-join-merge.nerolabs.workers.dev/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://dataset-join-merge.nerolabs.workers.dev/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "dataset-join-merge-mcp": {
      "serverUrl": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Dataset Join & Merge MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.