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.
https://dataset-join-merge.nerolabs.workers.dev/mcpWhat its tools do
2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Not annotated (2)
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
- 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
{
"tools": {
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
2 advertised
list_capabilities
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.
{
"type": "object",
"properties": {},
"additionalProperties": false
}join_rows
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.
{
"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
Resources
Not advertised
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.
- 2026-11-06: 1 of 1 checks answered
- 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.
Claude Code
claude mcp add --transport http dataset-join-merge-mcp https://dataset-join-merge.nerolabs.workers.dev/mcpCodex
codex mcp add dataset-join-merge-mcp --url https://dataset-join-merge.nerolabs.workers.dev/mcpCursor
{
"mcpServers": {
"dataset-join-merge-mcp": {
"url": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
}
}
}Cline
{
"mcpServers": {
"dataset-join-merge-mcp": {
"type": "streamableHttp",
"url": "https://dataset-join-merge.nerolabs.workers.dev/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"dataset-join-merge-mcp": {
"type": "http",
"url": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http dataset-join-merge-mcp https://dataset-join-merge.nerolabs.workers.dev/mcpClaude Desktop
https://dataset-join-merge.nerolabs.workers.dev/mcpWindsurf
{
"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.