Integration

Navigatr integration

Navigatr is a digital badge platform for recognising learning and skills. Create, update, publish and expire badges with their criteria, alignments, endorsements and tags; issue a badge to a person or organisation by user id or email; list, verify, revoke, correct and export the resulting badge assertions (Open Badges 2.0 and 3.0); push assertions issued on Credly or the Open University; and read users, providers and communities with their badges. The username and password login route and the bulk tag removal (its input format is undocumented) are not exposed. Authentication is a long-lived Personal Access Token created in Navigatr account settings (Personal access tokens), sent in the X-Access-Token header.

Connect Navigatr How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Navigatr

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.

Badge assertion, 11 operations

delete_badge_assertionDelete badge assertionDELETEDeletes a badge assertion. To withdraw a badge but keep its record, use revoke_badge_assertion instead.
get_badge_assertionGet badge assertionGETReturns one badge assertion. Recipient email and role are returned only to the recipient, the issuing organisation's admins and platform admins; other callers get a redacted public view.
get_badge_assertion_open_badgeGet badge assertion open badgeGETReturns a badge assertion in Open Badges format: version 2.0 (default) or 3.0, where 3.0 is a signed credential as JSON-LD (format json) or VC-JWT (format jwt).
issue_badgeIssue badgePUTIssues a badge to a person or organisation: provider_id is required, plus recipient_id, or recipient_email with first and last name (or qr_id, spydus_barcode_id). The recipient is emailed a claim link (claim_url).
list_badge_assertionsList badge assertionsGETLists issued badges (assertions), paginated, newest first by default. Filter by badge_id, provider_id, recipient_id, recipient_email, status or keyword. Admins see only their own organisation's assertions.
list_badge_assertions_of_badgeList badge assertions of badgeGETLists the assertions (issued copies) of one badge, paginated, newest first by default. Use list_badge_assertions to filter across badges by provider, recipient or email.
list_user_badgesList user badgesGETLists the badges a user has received (their badge assertions), paginated. Pass user_id 0 for the user that owns the access token. Recipient email and change requests are returned only to authorised admins.
push_external_badge_assertionPush external badge assertionPOSTRecords on Navigatr a badge assertion issued on an external platform (Credly, Open University): the badge is matched by badge_external_id and the recipient by email.
revoke_badge_assertionRevoke badge assertionPUTRevokes a badge assertion: its status becomes Revoked. Optionally give a revocation_reason.
update_badge_assertion_detailsUpdate badge assertion detailsPUTCorrects an issued badge assertion: recipient name or organisation, expiry date, grade or credits earned. Leave out a field to keep it. The recipient is emailed once unless skip_email is true.
verify_badge_assertionVerify badge assertionGETChecks a badge assertion against Open Badge criteria; works without authentication. verified is true when reasons is empty; each key of reasons names a failed check. Refused with 403 for a non-public (Pending) assertion.

Badge, 10 operations

create_badgeCreate badgePOSTCreates a badge (draft) for a provider: name and type are required. Optionally add criteria, alignments, endorsements and tags in the same call. Publish it with publish_badge before issuing.
delete_badgeDelete badgeDELETEDeletes a badge, for example when it is no longer available on the credentialing platform. Navigatr says to use it only in extremely rare circumstances; prefer expire_badge to stop new issuing.
expire_badgeExpire badgePUTExpires a badge: it can no longer be issued, but assertions already issued are kept.
get_badgeGet badgeGETReturns one badge with its criteria, alignments, endorsements, tags, providers and issuer.
get_badge_open_badgeGet badge open badgeGETReturns a badge as an Open Badges BadgeClass (name, description, image, criteria, tags, issuer), for export to other badge platforms.
list_badgesList badgesGETLists badges, paginated. Pass one of provider_id, community_id, qa_community_id or issuer_id; on the public API only badges of the token owner's own provider or community can be listed. Ordered by name unless order_by says otherwise.
list_community_badgesList community badgesGETLists the badges created by a community, paginated, ordered by name unless order_by says otherwise.
list_provider_badgesList provider badgesGETLists the badges created by a provider, paginated, ordered by name unless order_by says otherwise.
publish_badgePublish badgePUTPublishes a draft badge. While draft, only provider admins or the owner can see it; a published badge is visible to all users.
update_badgeUpdate badgePUTUpdates a badge. Partial update: send only the fields to change and leave out the others to keep their current values. design_parameters replaces the saved object whole.

Badge alignment, 5 operations

create_badge_alignmentCreate badge alignmentPOSTAdds one alignment (name, description and url required) to a badge. Refused with 422 for the alignment the badge's qualification level manages: change the qualification level instead.
create_badge_alignmentsCreate badge alignmentsPOSTAdds several alignments to a badge in one call; each item needs name, description and url. Refused with 422 for the alignment managed by the badge's qualification level.
delete_badge_alignmentDelete badge alignmentDELETEDeletes one alignment of a badge, identified by alignment_id from list_badge_alignments. Refused with 422 for the alignment managed by the badge's qualification level.
list_badge_alignmentsList badge alignmentsGETLists the alignments of a badge (links to external frameworks, standards or competencies the badge maps to).
update_badge_alignmentUpdate badge alignmentPUTUpdates one alignment of a badge, identified by alignment_id from list_badge_alignments. Refused with 422 for the alignment managed by the badge's qualification level.

Badge criterion, 5 operations

create_badge_criteriaCreate badge criteriaPOSTAdds several criteria to a badge in one call; each item needs a description and a type. Returns the badge's criteria.
create_badge_criterionCreate badge criterionPOSTAdds one criterion (description and type required) to a badge. Use create_badge_criteria to add several at once.
delete_badge_criterionDelete badge criterionDELETEDeletes one criterion of a badge, identified by criteria_id from list_badge_criteria.
list_badge_criteriaList badge criteriaGETLists the criteria of a badge (what a recipient must do to earn it).
update_badge_criterionUpdate badge criterionPUTUpdates one criterion of a badge, identified by criteria_id from list_badge_criteria. Leave out a field to keep its current value.

Badge endorsement, 5 operations

create_badge_endorsementCreate badge endorsementPOSTAdds one endorsement (name and description required) to a badge. Use create_badge_endorsements to add several at once.
create_badge_endorsementsCreate badge endorsementsPOSTAdds several endorsements to a badge in one call; each item needs a name and a description. Returns the badge's endorsements.
delete_badge_endorsementDelete badge endorsementDELETEDeletes one endorsement of a badge, identified by endorsement_id from list_badge_endorsements.
list_badge_endorsementsList badge endorsementsGETLists the endorsements of a badge (third parties vouching for it).
update_badge_endorsementUpdate badge endorsementPUTUpdates one endorsement of a badge, identified by endorsement_id from list_badge_endorsements. Leave out a field to keep its current value.

Badge tag, 4 operations

add_badge_tagAdd badge tagPOSTAdds one tag to a badge: name is required, type and source are optional. Use add_badge_tags to add several at once.
add_badge_tagsAdd badge tagsPOSTAdds several tags to a badge in one call; each item needs a name. A tag the badge already has is ignored.
list_badge_tagsList badge tagsGETLists the tags (skills, outcomes, interests and similar labels) attached to a badge.
remove_badge_tagRemove badge tagDELETERemoves one tag from a badge, identified by its name as returned by list_badge_tags.

Provider, 4 operations

get_providerGet providerGETReturns one provider (a training or content organisation that issues badges). Its own admins get the full record; other callers get a public view with the contact email.
get_provider_open_badge_issuerGet provider open badge issuerGETReturns a provider as an Open Badges issuer profile (id, name, url, email, description, image); works without authentication.
list_community_providersList community providersGETLists the providers of a community, paginated. Admins of the community get full provider records; other callers get public views.
list_user_providersList user providersGETLists the providers (badge-issuing organisations) a user belongs to; pass user_id 0 for the token owner. Set enable_badge_create to true to keep only providers where the user can create badges.

Change request, 2 operations

create_badge_assertion_change_requestCreate badge assertion change requestPOSTOpens a change request on your own badge assertion: list the fields to change in changes, with an optional note. Recipient only, one open request at a time; an issuing-org admin then reviews it.
review_badge_assertion_change_requestReview badge assertion change requestPUTApproves or rejects ONE requested field of a change request (issuing-org admin only). Approval only records the outcome: apply the value with update_badge_assertion_details.

Community, 2 operations

get_communityGet communityGETReturns one community. Platform admins and the community's own admins get the full record; other callers get a public view without contact details or settings.
list_user_communitiesList user communitiesGETLists the communities a user is associated with. Pass user_id 0 for the user that owns the access token.

User, 1 operation

get_userGet userGETReturns a user's profile. Pass user_id 0 for the user that owns the access token. Another user's address, location and private ids are omitted unless the caller is a platform admin.

User interest, 1 operation

add_user_interestsAdd user interestsPOSTAdds a list of interests (free-text names) to a user's profile. Pass user_id 0 for the user that owns the access token. Returns the user's interests.

User learning style, 1 operation

add_user_learning_stylesAdd user learning stylesPOSTAdds a list of learning styles (free-text names) to a user's profile. Pass user_id 0 for the user that owns the access token. Returns the user's learning styles.

Use Navigatr from Claude Code, Cursor or Codex

Connect Navigatr in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Navigatr 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 Navigatr

Create your workspace
Sign up free. Nothing to install.
Connect Navigatr once
Add your Navigatr 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.