Namely MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Other

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

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

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• 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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 39 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 17 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

• More stars than 0% of the other 32441 servers in this category
• Published to the registry more recently than 97% of the other 32441 servers in this category
• Basic checks equal to or better than 100% of the other 32441 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{