Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Namely MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
17
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http namely-mcp-by-usefulapi https://namely.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# namely_get_me, namely_list_profiles, namely_get_profile and 14 more
Namely MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 563 servers
usefulapi563 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http namely-mcp-by-usefulapi https://namely.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
No parameter schema on file.
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 may see (compensation, addresses and other sensitive HR data). An empty page means the end. Namely API: GET /profiles (lim
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1. |
| per_page | integer | no | Profiles per page (default 30, max 50). |
| format | string | no | short = truncated profile objects (default); full = every field. |
| sort | string | no | Sort order; a leading - reverses it. |
| user_status | string | no | Only profiles with this status. |
| first_name | string | no | Exact first name. |
| last_name | string | no | Exact last name. |
| string | no | Exact company email. | |
| personal_email | string | no | Exact personal email. |
| job_title | string | no | Exact job title (the title of a job title). |
| reports_to | string | no | Profile id of a manager: only that person's direct reports. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Namely profile id (the id of a profile from namely_list_profiles). |
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.
No parameter schema on file.
List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.
No parameter schema on file.
Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Group id (from namely_list_groups). |
List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.
No parameter schema on file.
List all teams with their team categories. Namely API: GET /teams.
No parameter schema on file.
Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Team id (from namely_list_teams). |
List all job titles; each belongs to one job tier. Namely API: GET /job_titles.
No parameter schema on file.
List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Event type, e.g. birthday, announcement, recent_arrival, anniversary. |
| profile_id | string | no | Only events associated with this profile id. |
| limit | integer | no | Number of events to return (max 30). |
| after | string | no | Event id after which to start (for the next page). |
| order | string | no | Order by time; default desc. |
List the comments on a feed event. Namely API: GET /events/{event-id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id (from namely_list_events). |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Report id. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Namely profile id (the id of a profile from namely_list_profiles). |
| first_name | string | no | First name. |
| last_name | string | no | Last name. |
| string | no | Company email. | |
| personal_email | string | no | Personal email (required when user_status is pending). |
| user_status | string | no | active or pending. |
| start_date | string | no | Start date, YYYY-MM-DD. |
| reports_to | string | no | Profile id of the new manager. |
| job_title | object | no | New job title: an object with the id or the exact title of an existing job title. |
Post an announcement to the company home feed, visible to every employee. Markdown; to mention a person write [Full Name](/people/<profile_id>). With is_appreciation, mentioned people are appreciated. email_all=true ALSO EMAILS every active employee at their company address (needs the permission) and cannot be undone: set it only when the user explicitly asks. Namely API: POST /events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | Announcement text in markdown. |
| is_appreciation | boolean | no | If true, mentioned profiles are appreciated. |
| email_all | boolean | no | If true, also emails all active employees. Default false. |
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/<profile_id>). Namely API: POST /events/{id}/comments.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | Event id (from namely_list_events). |
| content | string | yes | Comment text in markdown. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Namely MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.16.1 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestc57102a0bc1683c52aa8ce2270092b871de78e959518abfea7f5d32a18c5abd6
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| namely_get_me | no tags | |
| namely_list_profiles | no tags | |
| namely_get_profile | no tags | |
| namely_list_profile_fields | no tags | |
| namely_list_groups | no tags | |
| namely_get_group | no tags | |
| namely_list_group_types | no tags | |
| namely_list_teams | no tags | |
| namely_get_team | no tags | |
| namely_list_job_titles | no tags | |
| namely_list_job_tiers | no tags | |
| namely_list_events | no tags | |
| namely_list_event_comments | no tags | |
| namely_get_report | no tags | |
| namely_update_profile | state-write | state-write: declares destructiveHint: true |
| namely_create_announcement | state-write | state-write: declares destructiveHint: true |
| namely_create_event_comment | state-write | state-write: declares destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestc57102a0bc1683c5
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.16.1.
1.16.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Namely MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.