Kisi MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 旅行、地图与天气

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://kisi.usefulapi.io/mcp

claude mcp add --transport http kisi https://kisi.usefulapi.io/mcp

{
  "mcpServers": {
    "kisi": {
      "url": "https://kisi.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "kisi": {
      "type": "http",
      "url": "https://kisi.usefulapi.io/mcp"
    }
  }
}

https://kisi.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• kisi_get_current_user

  The Kisi user the API key belongs to (id, name, email, organization). Good first call. GET /user.

• kisi_get_organization

  The current Kisi organization (name, domain, settings summary). GET /organization.

• kisi_list_places

  List places (sites/buildings) in the organization with address, time zone and lock/member counts. GET /places.

• kisi_get_place

  One place by id, including lockdown state. GET /places/{id}.

• kisi_list_locks

  List locks/doors with their state: online, unlocked, locked_down, configured, place and floor. Filter to find offline or locked-down doors. GET /locks.

• kisi_get_lock

  One lock/door by id: online/unlocked/locked-down state, place, floor, settings. GET /locks/{id}.

• kisi_list_groups

  List access groups (who-can-open-what bundles of doors). Filter by place or by a lock to see which groups open that door. GET /groups.

• kisi_get_group

  One access group by id (name, description, place, member/lock counts, restrictions). GET /groups/{id}.

• kisi_list_group_locks

  The locks/doors an access group opens. GET /group_locks?group_id=.

• kisi_list_users

  List users (members) of the organization. Filter by group or place (users with access there), email, or free text over name/email/notes. Sort by last unlock. GET /users.

• kisi_get_user

  One user by id. GET /users/{id}.

• kisi_list_role_assignments

  Who holds which role where: a user/team/guest's role on the organization, a place or a group (group members = door access). Filter by user, group, place or role. GET /role_assignments.

• kisi_list_cards

  List access cards with status (activated/deactivated/unassigned), assignee and last use. GET /cards.

• kisi_list_presences

  Who was present at a place on a given day (derived from unlocks): actor, first/last unlock, last door. GET /presences.

• kisi_list_schedules

  Time rules: when a group's access is allowed, when doors auto-unlock (unlock timer), first-to-arrive, elevator permit timers. Filter by consequence or by the group/lock it applies to. GET /schedules.

• kisi_list_controllers

  Kisi controllers (door hardware hubs) with online/offline status. Filter by place, lock or status. GET /controllers.

• kisi_list_readers

  Kisi readers (card/phone readers at doors) with model and online/offline status. GET /readers.

• kisi_search_events

  Search the access log (unlocks, denied attempts, lockdowns, admin changes) and return the first page. This CREATES a temporary saved search in Kisi (an event set, cursor-paginated, kept ~24 h); it changes no door, user or access right. Defaults to the past 90 days, the maximum wi

• kisi_get_event_set

  Read an event set from kisi_search_events: its status and events. Pass the previous page's cursor for the next page. GET /event_sets/{id}.

• kisi_list_event_types

  All event type names usable as the type filter of kisi_search_events (e.g. lock.unlock). GET /events/types.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 5 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 20 个工具描述，未发现针对 AI 的隐藏指令

与“旅行、地图与天气”中的其他服务器比较i

• 星标数多于此分类中其他 1718 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1718 个服务器的 99% 更新
• 基础检查结果等于或优于此分类中其他 1718 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{