Join two lists of JSON rows on a key, like SQL or VLOOKUP: left, inner, full, anti joins, union.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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.
The LEFT table: the main rows you want to keep or enrich. Each row is a JSON object; keys may differ between rows.
The RIGHT table: the lookup rows to pull matching fields from. Each row is a JSON object.
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.
normalized (default): case-insensitive, trimmed, repeated spaces collapsed, 123 matches "123". exact: values must be identical.
Only copy these fields from the matching right row, like choosing VLOOKUP return columns. Leave out to copy every right field.
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.
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.
On by default: every row gets _joinStatus ("matched", "left_only", "right_only") and _matchCount. Set false for rows with only your own fields.
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.
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.
Prefix for conflicting right fields when onFieldConflict is prefixRight. Default "right_", so price becomes right_price.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
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.
| Argument | Type | Description |
|---|---|---|
| joinType | string | 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* | array | The LEFT table: the main rows you want to keep or enrich. Each row is a JSON object; keys may differ between rows. |
| rightRows* | array | The RIGHT table: the lookup rows to pull matching fields from. Each row is a JSON object. |
| keyMatching | string | normalized (default): case-insensitive, trimmed, repeated spaces collapsed, 123 matches "123". exact: values must be identical. |
| rightFields | array | Only copy these fields from the matching right row, like choosing VLOOKUP return columns. Leave out to copy every right field. |
| leftKeyFields | array | 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 | array | 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 | boolean | On by default: every row gets _joinStatus ("matched", "left_only", "right_only") and _matchCount. Set false for rows with only your own fields. |
| multipleMatches | string | 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 | string | 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 | string | Prefix for conflicting right fields when onFieldConflict is prefixRight. Default "right_", so price becomes right_price. |
{
"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
}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.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}