Dataset Join & Merge

Join two lists of JSON rows on a key, like SQL or VLOOKUP: left, inner, full, anti joins, union.

我该使用它吗

质量与安全性

A
描述质量
100%
模式完整度
65%
命名质量
90%
投毒风险
100%
权限匹配度
100%
协议合规性
100%

基于对工具定义和协议合规性的自动分析。

上下文开销

~899token 数(工具定义)
~4.1 KB典型响应大小
对注意力有中等影响(占 128k 上下文窗口的 0.70%)

这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。

安装

一键安装

将以下内容添加到你的 `claude_desktop_config.json` 文件中:

{
  "mcpServers": {
    "dataset-join-merge": {
      "url": "https://dataset-join-merge.nerolabs.workers.dev/mcp"
    }
  }
}

远程端点

https://dataset-join-merge.nerolabs.workers.dev/mcpstreamable-http

它能做什么

工具清单

工具(2)

🟢 只读🟡 写入🔴 删除⚪ 未知
🟢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(leftRows, rightRows, leftKeyFields, rightKeyFields, joinType, ...)

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",
  "properties": {
    "leftRows": {
      "type": "array",
      "description": "The LEFT table: the main rows you want to keep or enrich. Each row is a JSON object; keys may differ between rows.",
      "items": {
        "type": "object"
      }
    },
    "rightRows": {
      "type": "array",
      "description": "The RIGHT table: the lookup rows to pull matching fields from. Each row is a JSON object.",
      "items": {
        "type": "object"
      }
    },
    "leftKeyFields": {
      "type": "array",
      "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.",
      "items": {
        "type": "string"
      }
    },
    "rightKeyFields": {
      "type": "array",
      "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.",
      "items": {
        "type": "string"
      }
    },
    "joinType": {
      "type": "string",
      "enum": [
        "left",
        "inner",
        "right",
        "full",
        "leftAnti",
        "rightAnti",
        "union"
      ],
      "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."
    },
    "keyMatching": {
      "type": "string",
      "enum": [
        "normalized",
        "exact"
      ],
      "description": "normalized (default): case-insensitive, trimmed, repeated spaces collapsed, 123 matches \"123\". exact: values must be identical."
    },
    "rightFields": {
      "type": "array",
      "description": "Only copy these fields from the matching right row, like choosing VLOOKUP return columns. Leave out to copy every right field.",
      "items": {
        "type": "string"
      }
    },
    "onFieldConflict": {
      "type": "string",
      "enum": [
        "prefixRight",
        "keepLeft",
        "keepRight"
      ],
      "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."
    },
    "multipleMatches": {
      "type": "string",
      "enum": [
        "all",
        "first"
      ],
      "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."
    },
    "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."
    }
  },
  "required": [
    "leftRows",
    "rightRows"
  ],
  "additionalProperties": false
}

社区

评价此服务器

证据

最近观测

已验证未记录版本2 个工具
已验证未记录版本2 个工具
已验证未记录版本2 个工具