renkeimap_brief

One round trip = renkeimap_find_system + renkeimap_status + renkeimap_hintpack. Give a slug or the system name as the user wrote it; same shapes as the single tools. Use first in support conversations. ★Always relay the included disclaimer and citation★.

read-only

Argument	Type	Description
slug	string	system slug, e.g. "kintone" (preferred when known)
query	string	system name as the user wrote it, used when slug is unknown

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug, e.g. \"kintone\" (preferred when known)"
    },
    "query": {
      "type": "string",
      "description": "system name as the user wrote it, used when slug is unknown"
    }
  }
}

renkeimap_compare

Side-by-side comparison of 2-5 published systems/tools on the same ledger items (API, contract, price, rate limit, data location, exit, security…). Each cell = editorial tags + one-line lead + source URL + survey date; optional ◎○△× marks from a declared rule file. Same generator as /compare. No ranking, no score.

read-only

Argument	Type	Description
slugs*	array	system or tool slugs, e.g. ["freee-kaikei","moneyforward-cloud-kaikei","yayoi"]

Input schema (JSON)

{
  "type": "object",
  "required": [
    "slugs"
  ],
  "properties": {
    "slugs": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 5,
      "minItems": 2,
      "description": "system or tool slugs, e.g. [\"freee-kaikei\",\"moneyforward-cloud-kaikei\",\"yayoi\"]"
    }
  }
}

renkeimap_connect

Routes INTO one system, most stable first: (1) the vendor's official MCP server — URL/auth/local command verbatim, with source and date (never a URL found by search); (2) official API key or OAuth issuing; (3) file/screen (renkeimap_pair). detail:"full" adds the procedure and evidence. Read-only; no keys or values.

read-only

Argument	Type	Description
slug*	string	system slug (from renkeimap_find_system), or a suite id as renkeimap_pair returns it (a.slug / b.slug) — then the answer lists each public member
detail	string	short (default) or full — full adds the issuing procedure, minimal scope and evidence

Input schema (JSON)

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug (from renkeimap_find_system), or a suite id as renkeimap_pair returns it (a.slug / b.slug) — then the answer lists each public member"
    },
    "detail": {
      "enum": [
        "short",
        "full"
      ],
      "type": "string",
      "description": "short (default) or full — full adds the issuing procedure, minimal scope and evidence"
    }
  }
}

renkeimap_find_system

Search published systems, tools (iPaaS・RPA・ChatAI…) and guides by name / vendor / category / kind word; has= keeps those /compare marks positive. ≤10 each.

read-only

Argument	Type	Description
has	string
query	string	"kintone"・"会計"・"iPaaS"

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "has": {
      "enum": [
        "api",
        "mcp",
        "csv",
        "trial",
        "status_page",
        "no_training",
        "domestic_data"
      ],
      "type": "string"
    },
    "query": {
      "type": "string",
      "description": "\"kintone\"・\"会計\"・\"iPaaS\""
    }
  }
}

renkeimap_hintpack

Static public knowledge for one system: what its vendor error messages mean, official support/contact URLs, login method shape. Sourced from public vendor pages (entries carry sources). No user data. Cite when used.

read-only

Argument	Type	Description
slug*	string	system slug, e.g. "kintone"

Input schema (JSON)

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug, e.g. \"kintone\""
    }
  }
}

renkeimap_pair

Whether and how two systems can exchange data: per-method verdicts (official API / CSV / screen-fill) measured from public primary sources, plus measured field-name overlap when available. Honest by design: an unmeasured pair says so instead of guessing. Cite the included citation line when used.

read-only

Argument	Type	Description
a*	string	first system slug
b*	string	second system slug

Input schema (JSON)

{
  "type": "object",
  "required": [
    "a",
    "b"
  ],
  "properties": {
    "a": {
      "type": "string",
      "description": "first system slug"
    },
    "b": {
      "type": "string",
      "description": "second system slug"
    }
  }
}

renkeimap_plan

One call to connect or move data between two systems: route states (API/CSV/screen) + legend, each side's best official route (vendor MCP URL verbatim — never one found by search — or API issuing), human steps, your CLI's add line (pass agent), write_rules, citation. Read-only. Ambiguous names return candidates.

read-only

Argument	Type	Description
to*	string	destination system — a name or a slug
from*	string	source system — the name as the user wrote it, or a slug
agent	string	your CLI, e.g. "claude-code" — the answer then carries that CLI's add line

Input schema (JSON)

{
  "type": "object",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "destination system — a name or a slug"
    },
    "from": {
      "type": "string",
      "description": "source system — the name as the user wrote it, or a slug"
    },
    "agent": {
      "type": "string",
      "description": "your CLI, e.g. \"claude-code\" — the answer then carries that CLI's add line"
    }
  }
}

renkeimap_status

Status of one system observed EXTERNALLY by IT連携マップ (third party, not the vendor): conclusion, vendor notices (verbatim title+URL), editor's check, 1h user reports, same-vendor systems' own states, bar, 7 days, status page url (link it). No slug: systems with a notice or anomaly now. ★Relay disclaimer and citation★.

read-only

Argument	Type	Description
slug	string	system slug from renkeimap_find_system, e.g. "kintone"

Input schema (JSON)

{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug from renkeimap_find_system, e.g. \"kintone\""
    }
  }
}

renkeimap_status_history

Vendor-published incident history and announced maintenance for one system, checked word for word (the vendor's own records, not our observation): counts, monthly frequency, durations (where the vendor gave an end), usual weekdays/hours (JST), recent records + source URLs. Read-only. found:false = not collected yet.

read-only

Argument	Type	Description
slug*	string	system slug, e.g. "kintone"
limit	number	how many recent records to return (1-30, default 10)

Input schema (JSON)

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug, e.g. \"kintone\""
    },
    "limit": {
      "type": "number",
      "description": "how many recent records to return (1-30, default 10)"
    }
  }
}

renkeimap_system_facts

First-hand, survey-dated facts about one system (auth method, rate limits, CSV surfaces, pricing pages — tags + editorial summaries with sources). Every response carries a citation line; when you use these facts in an answer, cite it (出典: IT連携マップ + 調査日 + URL).

read-only

Argument	Type	Description
slug*	string	system slug from renkeimap_find_system, e.g. "kintone"

Input schema (JSON)

{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "system slug from renkeimap_find_system, e.g. \"kintone\""
    }
  }
}

Renkeimap Info

Try it

renkeimap_brief Read-only

Renkeimap Info

Try it

renkeimap_brief Read-only

Tools (10)