Integration

Certopus integration

Certopus creates and delivers digital credentials (certificates and badges) for courses, events and training programs. Issue credentials to recipients in an event category, generating them and emailing them to the recipients when asked, and list the organisations, events and categories they are issued under. Designs, mailing templates and events are set up in the Certopus app; the API documents no route to read, revoke or delete an issued credential. Authentication is an API key sent in the x-api-key header, created in Certopus under Organisation, API Management (with Read, Write or Admin permission).

Connect Certopus How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Certopus

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.

Category, 1 operation

list_categoriesList categoriesGETLists the credential categories of one event (id and title). A category carries the credential design and mailing setup; use its id as categoryId in create_credential.

Credential, 1 operation

create_credentialCreate credentialPOSTIssues credentials to recipients in an event category, using Certopus credits. generate=true creates the certificates now; publish=true also EMAILS them to the recipients. Returns each certificate's id and URLs.

Event, 1 operation

list_eventsList eventsGETLists the events of one Certopus organisation (id and title). Use an id as eventId in list_categories and create_credential.

Organisation, 1 operation

list_organisationsList organisationsGETLists the Certopus organisations of the user the API key belongs to: id, name, logo URL and the integrationAllowed flag. Use an id as organisationId in list_events and create_credential.

Use Certopus from Claude Code, Cursor or Codex

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

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