# Namely MCP Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Namely MCP

Access and manage employee profiles, teams, groups and company announcements in Namely.

- Record: https://musedirectory.ai/connector/namely-mcp
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/namely/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 168ms, checked 2026-10-29T22:36:24Z
- Endpoint: https://namely.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T22:36:24Z)
- Source: Found in the official MCP Registry (io.usefulapi/namely) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Fnamely

Connect to Namely HR software to read employee profiles, organizational structure, teams and job titles; update employee records and post announcements to the company feed. Requires Namely account and API token.

Example request: "Show me all employees in the engineering department and their managers."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Namely MCP to help me. It is a free service with an MCP server at https://namely.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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/<profile_id>). With is_appreciation, mentioned people are appreciated. email_all=true ALSO EMAILS every active employee at their company address (need
- 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/<profile_id>). Namely API: POST /events/{id}/comments.

Screening checks:
- MCP handshake: pass (Answered in 168ms)
- Domain against threat feeds (Cloudflare security DNS): pass (namely.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (17 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)