← All integrations

Paradym MCP server

33 operations1 webhook

Paradym is the easiest way to issue, verify, and manage verifiable credentials. This plugin manages wallets, SD-JWT VC credential templates and trusted entities, creates OpenID4VC issuance offers and verification requests, batch-revokes issued credentials, and manages webhook subscriptions with delivery history.

Try Paradym with your agent

Connect Paradym, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Paradym on my account, then run one read-only example and show me the result.

Runs once, when you ask

Paradym tools and triggers

Tools are what your agent can do in Paradym through Corsair's MCP server. Triggers are the Paradym events a routine can start from.

Credential Templates

  • ArchiveDestructive

    Archive an SD-JWT VC credential template

    credentialTemplates.archive

  • CreateWrite

    Create an SD-JWT VC credential template with its attributes

    credentialTemplates.create

  • GetRead-only

    Read one SD-JWT VC credential template

    credentialTemplates.get

  • ListRead-only

    List SD-JWT VC credential templates

    credentialTemplates.list

  • UnarchiveWrite

    Unarchive an SD-JWT VC credential template

    credentialTemplates.unarchive

  • UpdateWrite

    Update an SD-JWT VC credential template

    credentialTemplates.update

Webhooks

  • Create SubscriptionWrite

    Create a webhook subscription for the event types you choose

    webhooks.createSubscription

  • Delete SubscriptionDestructive

    Delete a webhook subscription; deliveries stop until it is created again

    webhooks.deleteSubscription

  • Get DeliveryRead-only

    Read one webhook delivery with its attempt history

    webhooks.getDelivery

  • List DeliveriesRead-only

    List webhook deliveries with their statuses

    webhooks.listDeliveries

  • List SubscriptionsRead-only

    List the wallet webhook subscriptions

    webhooks.listSubscriptions

  • Redeliver DeliveryDestructive

    Redeliver a pending or failed webhook delivery: the payload is posted to the subscription URL again

    webhooks.redeliverDelivery

Connect Paradym to Claude, ChatGPT or Cursor

  1. 1

    Connect Paradym in Corsair

    Add your Paradym API key once in Corsair. Corsair stores the credential encrypted and makes the Paradym API calls for your agent, so it never goes into a prompt or a config file. Connect Paradym

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Paradym. On a ChatGPT personal plan, connect Paradym here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Paradym's read and write operations run right away and its 6 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/paradym, add the Paradym plugin, and connect with an API key. Then call methods like corsair.paradym.api.credentialTemplates.archive() from your app. Corsair verifies webhooks, and keeps each tenant isolated.

Yes. Paradym requires an API key from your Paradym account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Paradym, GitHub, Notion, Stripe, and the rest. Trigger Paradym from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for paradym is the easiest way to issue, verify, and manage verifiable credentials. This plugin manages wallets, SD-JWT VC credential templates and trusted entities, creates OpenID4VC issuance offers and verification requests, batch-revokes issued credentials, and manages webhook subscriptions with delivery history. Common builds include sync jobs, admin tooling, and agents that call Paradym APIs from your backend. Webhook handlers react to Paradym events and fan out to Slack, email, or other plugins in the same tenant.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Paradym API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/paradym in the open repo. When Paradym ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Paradym data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Paradym data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Paradym on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 6 destructive Paradym operations. You can change a link's mode at hub.corsair.dev/me.