Namely MCP by usefulapi

它能帮你做什么

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

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

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

你需要

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

你用的是哪个应用？

https://namely.usefulapi.io/mcp

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

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

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

https://namely.usefulapi.io/mcp

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

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

它能做什么

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

• namely_get_me

  Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.

• namely_list_profiles

  List employee profiles (active, pending and inactive unless filtered) with paging, sorting and filters. Returns {profiles, meta:{count}, linked}. Use format=short for a smaller record (ids, names, email, status, job title); the full record includes every custom field the token ma

• namely_get_profile

  Get one employee's full profile by id: personal and job data, manager, groups, teams and the custom fields the token may see (can include compensation and other sensitive HR data). Namely API: GET /profiles/{id}.

• namely_list_profile_fields

  List the fields of the employee profile as configured at this company (standard and custom), with their labels, sections and the valid format of each value. Namely API: GET /profiles/fields.

• namely_list_groups

  List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.

• namely_get_group

  Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.

• namely_list_group_types

  List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.

• namely_list_teams

  List all teams with their team categories. Namely API: GET /teams.

• namely_get_team

  Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.

• namely_list_job_titles

  List all job titles; each belongs to one job tier. Namely API: GET /job_titles.

• namely_list_job_tiers

  List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.

• namely_list_events

  List events of the company home feed (announcements, birthdays, work anniversaries, new arrivals), newest first by default, with limit and after (an event id) for paging. Namely API: GET /events.

• namely_list_event_comments

  List the comments on a feed event. Namely API: GET /events/{event-id}/comments.

• namely_get_report

  Run a saved Namely report by id and return its columns and rows (live data; each row is a list in column order). Find the id in the URL of the report in Namely. Reports can contain sensitive HR data such as salary history. Namely API: GET /reports/{id}.

• namely_update_profile

  Change standard fields of an employee profile (name, emails, start date, status, manager, job title). WRITES live HR data. Send only the fields to change. Setting user_status to pending needs a personal_email. Namely API: PUT /profiles/{id}.

• namely_create_announcement

  Post an announcement to the company home feed, visible to every employee. Markdown; to mention a person write [Full Name](/people/ ). With is_appreciation, mentioned people are appreciated. email_all=true ALSO EMAILS every active employee at their company address (needs the permi

• namely_create_event_comment

  Add a comment to a feed event, posted as the token's user and visible to employees who see the event. Markdown; mention a person with [Full Name](/people/ ). Namely API: POST /events/{id}/comments.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 39 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

与“其他”中的其他服务器比较i

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

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

替代选择

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

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

作者的 README

{