Integration

Namely integration

Namely is an HR platform (HRIS). An agent can list, read, create and update employee profiles (including job title, home address and salary), read the current user's profile, read company info, countries, groups, group types, teams and notifications, manage job tiers and job titles, profile fields and profile field sections, read and post company announcements and comments, manage company resource folders, and run saved reports. Likes, file uploads and downloads, and resource deletion are not exposed. Profile reads return every standard field the token's user is allowed to see, which can include SSN, date of birth, salary and benefits; client-created custom fields are not part of the returned output. Authentication is a Namely Personal Access Token sent as a Bearer token, and the connection asks for the company subdomain (the part before .namely.com).

Connect Namely How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Namely.Built from the 45 Namely tools below, on the connection you add once.

What you can do with Namely

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Event, 4 operations

create_announcementCreate announcementPOSTPosts a company announcement to the Namely news feed, visible to the company; email_all=true also emails every active employee. Other event types are generated by Namely and cannot be created.
delete_eventDelete eventDELETEDeletes an event (for example an announcement) permanently.
get_eventGet eventGETReturns one event (announcement, birthday, anniversary, new arrival) with its content and linked profiles and comments.
list_eventsList eventsGETLists company events (announcements, birthdays, anniversaries, new arrivals), newest first, with the profiles that commented. Page with limit and after. Only events of active employees appear.

Field, 4 operations

create_profile_fieldCreate profile fieldPOSTCreates a custom profile field inside a profile field section.
get_profile_fieldGet profile fieldGETReturns one profile field.
list_profile_fieldsList profile fieldsGETLists every profile field configured for the company (standard and custom), with the format each value must take when sent in create_profile or update_profile.
update_profile_fieldUpdate profile fieldPUTChanges a profile field's label and/or moves it to another section. Leave a key out to keep its current value.

Folder, 4 operations

create_folderCreate folderPOSTCreates a company resource folder and returns the folders.
delete_folderDelete folderDELETEDeletes a company resource folder permanently.
list_foldersList foldersGETLists the company resource folders (shared document folders) with their titles and ids.
update_folderUpdate folderPUTRenames a company resource folder.

Job tier, 4 operations

create_job_tierCreate job tierPOSTCreates a job tier.
get_job_tierGet job tierGETReturns one job tier.
list_job_tiersList job tiersGETLists every job tier. Each job title belongs to exactly one job tier; a tier holds zero to many titles.
update_job_tierUpdate job tierPUTRenames a job tier.

Job title, 4 operations

create_job_titleCreate job titlePOSTCreates a job title under a job tier.
get_job_titleGet job titleGETReturns one job title with its job tier.
list_job_titlesList job titlesGETLists every job title with the job tier it belongs to. A profile's job_title is set with a title or id from here.
update_job_titleUpdate job titlePUTRenames a job title and/or moves it to another job tier.

Profile, 4 operations

create_profileCreate profilePOSTCreates an employee profile. user_status pending creates a draft onboarding session (Onboarding must be enabled). Also accepts job_title, home address and salary.
get_profileGet profileGETReturns one employee profile with the standard fields the token's user may see: name, emails, status, dates, job title, manager, groups, address, and possibly SSN, birth date, salary and benefits. Custom fields are not returned.
list_profilesList profilesGETLists active and inactive employee profiles, 30 per page by default, at most 50. Filter by name, email, job title, manager or status. Limited to 100 calls a minute (HTTP 406 beyond).
update_profileUpdate profilePUTUpdates an employee profile. Send only the fields to change; leave the others out to keep them.

Comment, 3 operations

create_event_commentCreate event commentPOSTPosts a comment on an event, visible to the company.
delete_event_commentDelete event commentDELETEDeletes one comment from an event permanently.
list_event_commentsList event commentsGETLists the comments posted on one event.

Section, 3 operations

get_profile_field_sectionGet profile field sectionGETReturns one profile field section with its fields.
list_profile_field_sectionsList profile field sectionsGETLists every profile field section configured for the company, with the profile fields in each under linked.fields.
update_profile_field_sectionUpdate profile field sectionPUTRenames a profile field section.

Country, 2 operations

get_countryGet countryGETReturns one country with its subdivisions (for example its states or provinces).
list_countriesList countriesGETLists every country Namely knows (fixed, not editable). Use a country id as country_id in a profile's home address.

Group, 2 operations

get_groupGet groupGETReturns one group with its group type and the profiles in it.
list_groupsList groupsGETLists every group (for example offices or departments). Each group belongs to exactly one group type, listed under linked.group_types.

Group type, 2 operations

get_group_typeGet group typeGETReturns one group type with the profiles associated with it.
list_group_typesList group typesGETLists every group type (for example Office or Department). Each group type holds zero to many groups.

Notification, 2 operations

list_notificationsList notificationsGETLists the notifications of the token's own user: time off, mentioned or appreciated, and generic ones. Keys vary by kind (comment_id only on a comment mention).
list_profile_notificationsList profile notificationsGETLists one profile's notifications, paginated (30 per page by default, at most 50).

Resource, 2 operations

list_folder_resourcesList folder resourcesGETLists the resource files in one company folder: title, file name, format, size, file URL and last edit.
list_resourcesList resourcesGETLists the company resource files that are not in any folder: title, file name, format, size, file URL and last edit.

Team, 2 operations

get_teamGet teamGETReturns one team with its categories.
list_teamsList teamsGETLists every team, with the team categories each one belongs to under linked.categories.

Info, 1 operation

get_company_infoGet company infoGETReturns the company's name, permalink (its subdomain before namely.com), login background and logo images, and the sign-in methods it allows (email_password, google_oauth2 or saml).

Me, 1 operation

get_current_profileGet current profileGETReturns the profile of the user who owns the access token, in the same format as get_profile (standard fields only, custom fields are not returned).

Report, 1 operation

get_reportGet reportGETRuns a saved Namely report live: report info, columns (in order), and content rows as arrays of values in column order. Read columns by name, not label. Keep under about 200 rows.

Use Namely from Claude Code, Cursor or Codex

Connect Namely in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Namely operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Namely

Create your workspace
Sign up free. Nothing to install.
Connect Namely once
Add your Namely connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.