MCP Server

Certifier provides a remote MCP server that lets compatible AI clients interact with your Certifier workspace straight from your chat interface.

Remote MCP server URL

https://api.certifier.io/v1/mcp

Features Overview

With the Certifier MCP server, users can do everything that is possible through the Public API in a familiar environment of a chat interface, including:

search, list, and inspect existing credentials
create, issue and send credentials
create and manage groups (credential templates)
list and inspect created designs

Requirements

To connect successfully, you need:

a Certifier account with access to at least one workspace
an MCP client that supports remote MCP over HTTP with OAuth

Connect the Server

To connect a compatible MCP client:

Add the remote MCP server URL: https://api.certifier.io/v1/mcp
Start the connection flow in your MCP client.
Sign in to Certifier if prompted.
Choose the workspace you want to authorize.
Approve the requested access.
Return to your MCP client and start using Certifier tools.

Claude Code

To add Certifier MCP server to Claude Code, use this command:

claude mcp add --transport http certifier https://api.certifier.io/v1/mcp

Authentication flow is then available from within Claude Code, using /mcp command and navigating to Certifier MCP.

Codex

To add Certifier MCP server to Codex, use this command:

codex mcp add certifier --url https://api.certifier.io/v1/mcp

The authentication flow should start automatically.

OpenCode

To add Certifier MCP server to OpenCode, use this command:

opencode mcp add

An interactive flow will guide you through the process:

Select Current project/Global depending on your needs
We recommend Certifier as MCP server name
Select Remote as MCP server type
Enter https://api.certifier.io/v1/mcp as server URL
Select Yes when asked if the server requires OAuth authentication
Select No when asked if you have a pre-registered client ID

Then start the authentication flow with

opencode mcp auth certifier

Authentication

The Certifier MCP server uses the standard OAuth authorization code flow for remote MCP servers.

Certifier publishes discovery documents that compatible clients can use automatically:

Authorization server metadata: https://api.certifier.io/.well-known/oauth-authorization-server
Protected resource metadata: https://api.certifier.io/.well-known/oauth-protected-resource/v1/mcp

Compatible clients can use OAuth discovery and dynamic client registration automatically. You do not need a pre-registered client ID for the standard connection flow.

Certifier supports the mcp:read and mcp:write scopes. Read-only actions use mcp:read; actions that create, update, issue, send, or delete data require mcp:write.

Common Use Cases

Here are some example requests you can make from a compatible MCP client after connecting Certifier.

Issue and Send a Credential

Issue and email a certificate to Jane Doe at jane@example.com for completing Product Training. Use the "Product Training 2026" group (credential template).

This is useful when you want to generate and deliver a credential in one step without leaving the chat.

Search for Existing Credentials

Find credentials issued to recipients from acme.com and show me the most recent ones first.

This helps with audits, support requests, and checking whether a credential has already been issued.

Create a Group (Credential Template) for a New Program

Create a group called "Leadership Academy Spring 2026" and attach the specified certificate and badge designs.

Use this when you are setting up a new course, cohort, event, or certification program in Certifier.

Inspect Available Designs

List my available designs and show me the details for the one best suited for employee certifications.

This is helpful when choosing which design to use before issuing credentials at scale.

Update or Resend a Credential

Find the credential for Alex Jonhson, update the recipient's name to Alex Johnson, and send it again by email.

This is useful for credential corrections, renewals, and support workflows.

Privacy

When you connect an MCP client to Certifier, that client can send authorized tool requests to Certifier on your behalf for the workspace you approved.

Data sent through the MCP client is processed by Certifier to fulfill your requests and is subject to Certifier's legal terms and privacy practices:

Only connect trusted MCP clients and only send data you want Certifier to process.

Support

If you need help connecting or using the Certifier MCP server:

Support Center: https://support.certifier.io/
Email: support@certifier.io

When contacting support, include:

the MCP client you are using
the workspace involved
the approximate time of the failed request
the action you were trying to perform

Notes

The Certifier MCP server is intended for clients that support remote MCP over HTTP and OAuth.
Tool availability depends on the data and permissions available in the workspace you authorize.
If access expires or is revoked, reconnect the server and complete the OAuth flow again.

On this page