Certifier
Certifier is a platform that enables organizations to create, manage, and issue digital certificates and credentials.
Verdict
Common use cases
- Issue course completion certificates after webinars
- Track which recipients opened their credentials
- Automate badge delivery for event attendees
- Pull credential interaction logs for compliance
- Send personalized certificates to training cohorts
Integration
- Vendor
- Certifier
- Category
- docs
- Auth
- API_KEY
- Tools
- 6
- Composio slug
certifier
Tools
- Create, issue, and send credential
Tool to create, issue, and send a credential in a single request. use when group id and recipient details are ready.
- List Credential Interactions
Tool to list credential interactions. use when you need to retrieve interaction events for a specific credential, with optional filtering and pagination.
- List Credentials
Tool to list credentials. use after authentication to retrieve paginated credentials.
- List Designs
Tool to list all designs. use after authentication to retrieve certificate and badge designs with pagination.
- List Groups
Tool to list all groups. use when you need to retrieve groups with pagination (limit and cursor).
- Send a Credential
Tool to send a published credential via email. use after confirming the credential is published.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations tab. 2. Click 'Add Integration' and select Certifier from the list. 3. Log in to your Certifier dashboard, go to Settings → API, and generate a new API key with 'Credentials: Write' and 'Groups: Read' scopes. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Return to any Space and type '@Certifier list designs' to confirm the connection — you should see your certificate templates appear. 6. To issue a credential, use '@Certifier create, issue, and send credential' followed by the group ID and recipient details; the MCP will handle the full workflow in one call.
What teammates see: by default, memories from Certifier are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Active Designs
@Certifier list all available designs, showing the design ID and name for each template.Open in a Space →
Issue Batch Certificates
@Certifier create, issue, and send credentials for group ID 12345 to these recipients: alice@example.com, bob@example.com, carol@example.com.Open in a Space →
Check Credential Status
@Certifier list the last 50 credentials issued, ordered by creation date.Open in a Space →
Track Recipient Engagement
@Certifier list all interactions for credential ID abc-123, including timestamps and event types.Open in a Space →
Review Credential Groups
@Certifier list all groups with their IDs and names, paginated with a limit of 20.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@certifier list all available certificate designs for our Q1 training program, showing the most recently created ones first
Found 12 certificate designs in your Certifier account. The three most recent are: 'Q1 Product Training Certificate' (created Feb 2, 2024), 'Sales Onboarding Badge' (created Jan 28, 2024), and 'Leadership Workshop Completion' (created Jan 15, 2024). Each design includes template ID, name, creation date, and whether it's currently active. This illustrative example shows how the MCP surfaces your design library for selection before issuing credentials.
This read operation requires a valid API key with design-read permissions. Useful for auditing what templates exist before bulk-issuing credentials. The MCP paginates results if you have more than 50 designs; specify a cursor to retrieve additional pages.
@certifier create and send a completion certificate to jane.doe@example.com using group ID 'training-cohort-5' with her name and completion date March 15 2024
Created credential ID cred_abc123 for Jane Doe in group 'training-cohort-5', issued it with completion date March 15, 2024, and sent the certificate via email to jane.doe@example.com. The recipient will receive a branded email with a link to view and download their credential. This illustrative example demonstrates the single-request workflow for issuing credentials when you already know the group ID and recipient details.
This write operation immediately sends an email to the recipient. Verify the group ID and recipient email before running—there's no undo. Requires API key permissions for credential creation and email sending. Rate limits apply if issuing credentials in bulk; batch large cohorts across multiple requests.
@certifier pull all credential interactions for certificate cred_xyz789 and summarize when and how the recipient engaged with it
Retrieved 4 interaction events for credential cred_xyz789. The recipient first viewed the certificate on March 16, 2024 at 10:23 AM, downloaded the PDF 6 minutes later, shared it to LinkedIn on March 17 at 2:15 PM, and viewed it again on March 20. This illustrative example shows how the MCP surfaces engagement data, which the AI can then synthesize into a timeline narrative for reporting or follow-up outreach.
Interaction tracking depends on the recipient's activity—credentials that haven't been opened yet return an empty list. Useful for measuring engagement after a cohort completes training. The MCP supports filtering by event type (view, download, share) if you need specific metrics.
Use-case deep-dives
When Certifier beats manual certificate workflows for customer training
A 10-person SaaS company runs monthly product certification webinars for new customers. Before Certifier, the CS team exported attendee lists from Zoom, manually filled certificate templates in Canva, and emailed PDFs one by one—burning 90 minutes per cohort. With this MCP, the team creates a design once, then uses 'Create, issue, and send credential' to batch-issue certificates directly from their CRM or a Slack command. The MCP handles the entire flow: credential creation, PDF generation, and email delivery. This wins when you issue 20+ credentials per month and your recipients expect professional, verifiable certificates. If you're only issuing 5 certificates a quarter, the setup overhead isn't worth it—stick with Canva and manual sends.
How Certifier scales partner tiering without spreadsheet chaos
A 6-person partnerships team manages a three-tier partner program (Bronze, Silver, Gold) with 80 active partners. Each tier earns a digital badge that partners display on LinkedIn and their websites. The team previously tracked badge eligibility in a Google Sheet and manually emailed badge images when partners hit milestones. Now they use 'List Groups' to organize partners by tier and 'Send a Credential' to issue badges when a partner upgrades. The MCP's interaction tracking ('List Credential Interactions') shows which partners actually claimed their badges, surfacing engagement gaps. This setup works when you have 30+ badge recipients and need audit trails for compliance or partner reporting. Below 30 recipients, the API_KEY setup and group management overhead outweighs the time saved.
When Certifier handles conference speaker certificates at scale
A 4-person events team runs quarterly industry conferences with 40-60 speakers per event. Speakers expect professional certificates within 48 hours of their talk. The team uses 'List Designs' to pull the current event's certificate template, then 'Create, issue, and send credential' to batch-issue certificates from their speaker roster spreadsheet. The MCP's single-request flow (create + issue + send) eliminates the three-step manual process they used with their old platform. This wins when you issue credentials in predictable batches (events, cohorts, milestones) and need consistent branding across hundreds of certificates per year. If your credential volume is under 50 annually or you need complex conditional logic before issuance, the MCP's batch-first design may feel rigid—consider a Zapier integration instead.
Frequently asked
What does the Certifier MCP do in Switchy?
It lets your AI agents create, issue, and send digital credentials — certificates, badges, course completions — directly from Switchy conversations. Instead of logging into Certifier's dashboard, you describe what credential you need, and the MCP handles design selection, recipient details, and email delivery. Useful for training teams, event organisers, or anyone issuing credentials at scale.
Do I need admin access to connect Certifier?
You need a Certifier API key, which typically requires account owner or admin permissions to generate. The key grants full access to create, issue, and send credentials across all your groups and designs, so treat it like a password. If your Certifier account has role-based access controls, check that your role can generate API keys before connecting.
Can the MCP revoke or edit credentials after they're issued?
No. The tools focus on creation, issuance, and sending. Once a credential is published and sent, you'll need to log into Certifier's web interface to revoke, update recipient details, or regenerate a certificate. The MCP also can't bulk-import recipients from a spreadsheet — you pass recipient data one credential at a time through the conversation.
Why use this instead of Certifier's dashboard or API directly?
The MCP removes the need to remember group IDs, design IDs, or API endpoint syntax. You tell your agent "issue a completion certificate to Jane Doe for the Q1 training", and it queries your groups and designs, matches the right template, and sends the credential. Faster than clicking through the dashboard; simpler than writing API scripts for one-off tasks.
Who on the team should connect the Certifier MCP?
Whoever manages your credential issuance workflow — typically a training coordinator, event manager, or ops lead. Because the API key grants full create-and-send permissions, avoid sharing the Switchy workspace with people who shouldn't issue credentials on your organisation's behalf. Each credential sent counts against your Certifier plan limits, so monitor usage if multiple teammates use the integration.