Namely MCP by usefulapi is an MCP server published by io.usefulapi, hosted at namely.usefulapi.io. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 17 tools, including namely_get_me, namely_list_profiles, namely_get_profile, namely_list_profile_fields, namely_list_groups.
Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.
4,305 connections through 5 shared values. Tap any node.
Inferred from the host name and headers: what a server runs on, not who runs it.
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
No parameters.
{
"name": "namely_get_me",
"title": "Get my profile",
"description": "Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "Get my profile",
"readOnlyHint": true
}
}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 (limit 100 requests per minute).
None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
| Parameter | Type | Description |
|---|---|---|
| page | integer | Page number, starting at 1. |
| sort | string | Sort order; a leading - reverses it. |
| string | Exact company email. | |
| format | string | short = truncated profile objects (default); full = every field. |
| per_page | integer | Profiles per page (default 30, max 50). |
| job_title | string | Exact job title (the `title` of a job title). |
| last_name | string | Exact last name. |
| first_name | string | Exact first name. |
| reports_to | string | Profile id of a manager: only that person's direct reports. |
| user_status | string | Only profiles with this status. |
| personal_email | string | Exact personal email. |
{
"name": "namely_list_profiles",
"title": "List employee profiles",
"description": "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 (limit 100 requests per minute).",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"page": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 1,
"description": "Page number, starting at 1."
},
"sort": {
"enum": [
"first_name",
"-first_name",
"last_name",
"-last_name",
"created_at",
"-created_at",
"updated_at",
"-updated_at"
],
"type": "string",
"description": "Sort order; a leading - reverses it."
},
"email": {
"type": "string",
"description": "Exact company email."
},
"format": {
"enum": [
"short",
"full"
],
"type": "string",
"description": "short = truncated profile objects (default); full = every field."
},
"per_page": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Profiles per page (default 30, max 50)."
},
"job_title": {
"type": "string",
"description": "Exact job title (the `title` of a job title)."
},
"last_name": {
"type": "string",
"description": "Exact last name."
},
"first_name": {
"type": "string",
"description": "Exact first name."
},
"reports_to": {
"type": "string",
"description": "Profile id of a manager: only that person's direct reports."
},
"user_status": {
"enum": [
"active",
"pending",
"inactive"
],
"type": "string",
"description": "Only profiles with this status."
},
"personal_email": {
"type": "string",
"description": "Exact personal email."
}
}
},
"annotations": {
"title": "List employee profiles",
"readOnlyHint": true
}
}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 | Description |
|---|---|---|
| id * | string | Namely profile id (the `id` of a profile from namely_list_profiles). |
{
"name": "namely_get_profile",
"title": "Get employee profile",
"description": "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}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Namely profile id (the `id` of a profile from namely_list_profiles)."
}
}
},
"annotations": {
"title": "Get employee profile",
"readOnlyHint": true
}
}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 parameters.
{
"name": "namely_list_profile_fields",
"title": "List profile fields",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List profile fields",
"readOnlyHint": true
}
}List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.
No parameters.
{
"name": "namely_list_groups",
"title": "List groups",
"description": "List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List groups",
"readOnlyHint": true
}
}Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Group id (from namely_list_groups). |
{
"name": "namely_get_group",
"title": "Get group",
"description": "Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Group id (from namely_list_groups)."
}
}
},
"annotations": {
"title": "Get group",
"readOnlyHint": true
}
}List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.
No parameters.
{
"name": "namely_list_group_types",
"title": "List group types",
"description": "List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List group types",
"readOnlyHint": true
}
}List all teams with their team categories. Namely API: GET /teams.
No parameters.
{
"name": "namely_list_teams",
"title": "List teams",
"description": "List all teams with their team categories. Namely API: GET /teams.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List teams",
"readOnlyHint": true
}
}Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.
| Parameter | Type | Description |
|---|---|---|
| id * | string | Team id (from namely_list_teams). |
{
"name": "namely_get_team",
"title": "Get team",
"description": "Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Team id (from namely_list_teams)."
}
}
},
"annotations": {
"title": "Get team",
"readOnlyHint": true
}
}List all job titles; each belongs to one job tier. Namely API: GET /job_titles.
No parameters.
{
"name": "namely_list_job_titles",
"title": "List job titles",
"description": "List all job titles; each belongs to one job tier. Namely API: GET /job_titles.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List job titles",
"readOnlyHint": true
}
}List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.
No parameters.
{
"name": "namely_list_job_tiers",
"title": "List job tiers",
"description": "List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
},
"annotations": {
"title": "List job tiers",
"readOnlyHint": true
}
}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 | Description |
|---|---|---|
| type | string | Event type, e.g. birthday, announcement, recent_arrival, anniversary. |
| after | string | Event id after which to start (for the next page). |
| limit | integer | Number of events to return (max 30). |
| order | string | Order by time; default desc. |
| profile_id | string | Only events associated with this profile id. |
{
"name": "namely_list_events",
"title": "List feed events",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"type": {
"type": "string",
"description": "Event type, e.g. birthday, announcement, recent_arrival, anniversary."
},
"after": {
"type": "string",
"description": "Event id after which to start (for the next page)."
},
"limit": {
"type": "integer",
"maximum": 30,
"minimum": 1,
"description": "Number of events to return (max 30)."
},
"order": {
"enum": [
"asc",
"desc"
],
"type": "string",
"description": "Order by time; default desc."
},
"profile_id": {
"type": "string",
"description": "Only events associated with this profile id."
}
}
},
"annotations": {
"title": "List feed events",
"readOnlyHint": true
}
}List the comments on a feed event. Namely API: GET /events/{event-id}/comments.
| Parameter | Type | Description |
|---|---|---|
| event_id * | string | Event id (from namely_list_events). |
{
"name": "namely_list_event_comments",
"title": "List event comments",
"description": "List the comments on a feed event. Namely API: GET /events/{event-id}/comments.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"minLength": 1,
"description": "Event id (from namely_list_events)."
}
}
},
"annotations": {
"title": "List event comments",
"readOnlyHint": true
}
}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 | Description |
|---|---|---|
| id * | string | Report id. |
{
"name": "namely_get_report",
"title": "Get report",
"description": "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}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Report id."
}
}
},
"annotations": {
"title": "Get report",
"readOnlyHint": true
}
}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 | Description |
|---|---|---|
| id * | string | Namely profile id (the `id` of a profile from namely_list_profiles). |
| string | Company email. | |
| job_title | object | New job title: an object with the id or the exact title of an existing job title. |
| last_name | string | Last name. |
| first_name | string | First name. |
| reports_to | string | Profile id of the new manager. |
| start_date | string | Start date, YYYY-MM-DD. |
| user_status | string | active or pending. |
| personal_email | string | Personal email (required when user_status is pending). |
{
"name": "namely_update_profile",
"title": "Update employee profile",
"description": "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}.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Namely profile id (the `id` of a profile from namely_list_profiles)."
},
"email": {
"type": "string",
"minLength": 3,
"description": "Company email."
},
"job_title": {
"type": "object",
"properties": {
"id": {
"type": "string",
"minLength": 1,
"description": "Job title id (guid, from namely_list_job_titles)."
},
"title": {
"type": "string",
"minLength": 1,
"description": "Exact job title text (case-sensitive)."
}
},
"description": "New job title: an object with the id or the exact title of an existing job title."
},
"last_name": {
"type": "string",
"minLength": 1,
"description": "Last name."
},
"first_name": {
"type": "string",
"minLength": 1,
"description": "First name."
},
"reports_to": {
"type": "string",
"minLength": 1,
"description": "Profile id of the new manager."
},
"start_date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Start date, YYYY-MM-DD."
},
"user_status": {
"enum": [
"active",
"pending"
],
"type": "string",
"description": "active or pending."
},
"personal_email": {
"type": "string",
"minLength": 3,
"description": "Personal email (required when user_status is pending)."
}
}
},
"annotations": {
"title": "Update employee profile",
"idempotentHint": true,
"destructiveHint": true
}
}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 | Description |
|---|---|---|
| content * | string | Announcement text in markdown. |
| email_all | boolean | If true, also emails all active employees. Default false. |
| is_appreciation | boolean | If true, mentioned profiles are appreciated. |
{
"name": "namely_create_announcement",
"title": "Post announcement",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"content"
],
"properties": {
"content": {
"type": "string",
"maxLength": 10000,
"minLength": 1,
"description": "Announcement text in markdown."
},
"email_all": {
"type": "boolean",
"description": "If true, also emails all active employees. Default false."
},
"is_appreciation": {
"type": "boolean",
"description": "If true, mentioned profiles are appreciated."
}
}
},
"annotations": {
"title": "Post announcement",
"destructiveHint": true
}
}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 | Description |
|---|---|---|
| content * | string | Comment text in markdown. |
| event_id * | string | Event id (from namely_list_events). |
{
"name": "namely_create_event_comment",
"title": "Comment on event",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id",
"content"
],
"properties": {
"content": {
"type": "string",
"maxLength": 10000,
"minLength": 1,
"description": "Comment text in markdown."
},
"event_id": {
"type": "string",
"minLength": 1,
"description": "Event id (from namely_list_events)."
}
}
},
"annotations": {
"title": "Comment on event",
"destructiveHint": true
}
}Tools for Namely, hosted by usefulapi.io. If the user is new or asks what this server can do, suggest requests such as: "Who reports to Jane Smith, and what are their job titles?"; "List everyone in the Sales department with their start dates."; "Which employees have a work anniversary or birthday coming up?". Read-only tools never change data; ask the user before a tool that creates, changes or deletes Namely data. Free plan: 50 tool calls per month. Run namely_usage_status to see the calls used this month. If the user asks for something none of these tools can do, tell the user and, with their OK, run namely_request_feature to record the request. Paid plans: Pro (10,000 tool calls a month, $9/month or $90/year, for normal use) and Pro+ (100,000 tool calls a month, $39/month or $390/year, for automations and heavy use). A plan can be cancelled at any time and then runs to the end of the paid period, so it also suits a one-time job. When the user wants more calls or reaches the limit, run namely_upgrade without a plan: it returns both plans, each with a payment link for the user to open. namely_cancel_subscription cancels Pro at the end of the paid period.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.