namely_get_me
Get my profile
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
Takes no parameters.
io.usefulapiPublished by usefulapi.ioOfficial publisherv1.16.3Updated Nov 5, 2026
Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.
The publisher's own server: Ably MCP by usefulapi
Hosted Namely HRIS connector that lets an assistant read employee profiles, org structure, jobs and reports, and make limited profile and feed updates.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.usefulapi%2Fnamely/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"namely-by-usefulapi": {
"type": "http",
"url": "https://namely.usefulapi.io/mcp"
}
}
}Read Namely employee profiles, groups, teams, jobs and reports; update profiles, post to the feed.
Live endpoint: https://namely.usefulapi.io/mcp · Homepage: https://usefulapi.io/namely
https://namely.usefulapi.io/mcp.claude mcp add --transport http namely https://namely.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Namely credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/namely/
On first connect you'll enter your Namely site name (acme for acme.namely.com) and a Personal Access Token.
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with namely_upgrade (it returns a Stripe Checkout link). Cancel any time with namely_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running namely_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Namely.
Source: servers/namely/README.md at commit 4046075
Get my profile
Get the profile of the user the connected token belongs to (name, email, job title, manager, access role). Namely API: GET /profiles/me.
Takes no parameters.
List employee 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 may see (compensation, addresses and other sensitive HR data). An empty page means the end. Namely API: GET /profiles (limit 100 requests per minute).
pagesortemailformatper_pagejob_titlelast_namefirst_namereports_touser_statuspersonal_emailGet employee 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}.
idrequiredList 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.
Takes no parameters.
List groups
List all groups (departments, office locations and other company groups). Every group belongs to one group type. Namely API: GET /groups.
Takes no parameters.
Get group
Get one group by id, with the profiles (members) linked to it. Namely API: GET /groups/{id}.
idrequiredList group types
List the group types (the containers of groups, such as Department or Office). Namely API: GET /group_types.
Takes no parameters.
List teams
List all teams with their team categories. Namely API: GET /teams.
Takes no parameters.
Get team
Get one team by id, with the profiles (members) linked to it. Namely API: GET /teams/{id}.
idrequiredList job titles
List all job titles; each belongs to one job tier. Namely API: GET /job_titles.
Takes no parameters.
List job tiers
List all job tiers (the levels that group job titles). Namely API: GET /job_tiers.
Takes no parameters.
List feed 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.
typeafterlimitorderprofile_idList event comments
List the comments on a feed event. Namely API: GET /events/{event-id}/comments.
event_idrequiredGet 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}.
idrequiredUpdate employee 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}.
idrequiredemailjob_titlelast_namefirst_namereports_tostart_dateuser_statuspersonal_emailPost 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 (needs the permission) and cannot be undone: set it only when the user explicitly asks. Namely API: POST /events.
contentrequiredemail_allis_appreciationComment on event
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.
contentrequiredevent_idrequired100% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
io.usefulapiOfficial publisher
Hosted MCP server for Ably that lets an assistant inspect realtime channels, presence and usage stats, publish messages, and review app configuration.
io.usefulapiOfficial publisher
Hosted ProofHub connector that lets an assistant read projects, tasks, comments, people and time entries, and create tasks or comments.
io.usefulapiOfficial publisher
Hosted, read-only MCP server that lets an assistant browse one MyOnlineStore shop's orders, products, categories, customers, discounts and newsletter…
io.usefulapiOfficial publisher
Hosted MCP server for Jostle Tasks: read users, presets, tasks and comments, and create or update tasks and post comments as your own user.
io.usefulapiOfficial publisher
Hosted MCP server for ExpenseOnDemand: read accounting exports, payroll totals and master data, and add, update or deactivate employees, customers and cost…
{ "mcpServers": { "namely": { "url": "https://namely.usefulapi.io/mcp" } }}