← All integrations

SignPath MCP server

34 operations0 webhooks

Code signing through SignPath - browse and change projects, signing policies, artifact configurations and certificates, then submit artifacts and hashes for signing, poll their status, approve or deny them, and read the audit log.

Try SignPath with your agent

Connect SignPath, 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 SignPath on my account, then run one read-only example and show me the result.

Runs once, when you ask

SignPath tools and triggers

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

Signing Requests

  • ApproveDestructive

    Approve a signing request waiting for approval; SignPath accepts it once the policy's required approval count is reached

    signingRequests.approve

  • CancelDestructive

    Cancel a signing request that has not finished; a cancelled request cannot be resumed, so a new one has to be submitted

    signingRequests.cancel

  • DenyDestructive

    Deny a signing request, which immediately marks it rejected; a denied request cannot be approved afterwards

    signingRequests.deny

  • GetRead-only

    Read one signing request with its status, workflow status, artifact links and verified origin when the build system provided one

    signingRequests.get

  • Get StatusRead-only

    Read only a signing request's status and workflow status, which is the cheap poll while it waits for approval or processing

    signingRequests.getStatus

  • ListRead-only

    List signing requests with filters for project, policy, configuration, certificate, status and submission time; follow pagination.nextLink for the next page

    signingRequests.list

  • ResubmitDestructive

    Resubmit a completed signing request under another policy, which is how a test-signed artifact is promoted to release signing; returns the new request id from the Location header

    signingRequests.resubmit

  • Sign HashDestructive

    Sign a hash with the policy's key and return the signature in the response, without an artifact or a waiting period

    signingRequests.signHash

  • Sign MessageDestructive

    Sign a message with ML-DSA and return the signature in the response; PureMldsa is the only algorithm SignPath offers here

    signingRequests.signMessage

  • Submit With ArtifactDestructive

    Submit an artifact for signing, uploading the bytes in the same call; the request then waits for approval and processing

    signingRequests.submitWithArtifact

  • Submit With Artifact Retrieval LinkDestructive

    Submit a signing request that points at an artifact SignPath downloads itself, which is the route for artifacts too large to upload

    signingRequests.submitWithArtifactRetrievalLink

  • Submit Without ArtifactDestructive

    Submit a signing request before the artifact exists, returning the upload link the artifact must be delivered to

    signingRequests.submitWithoutArtifact

Connect SignPath to Claude, ChatGPT or Cursor

  1. 1

    Connect SignPath in Corsair

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

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs SignPath. On a ChatGPT personal plan, connect SignPath 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, SignPath's read and write operations run right away and its 9 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/signpath, add the SignPath plugin, and connect with an API key. Then call methods like corsair.signpath.api.artifactConfigurations.activate() from your app. Corsair keeps each tenant isolated.

Yes. SignPath requires an API key from your SignPath 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 SignPath, GitHub, Notion, Stripe, and the rest. Trigger SignPath from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for code signing through SignPath - browse and change projects, signing policies, artifact configurations and certificates, then submit artifacts and hashes for signing, poll their status, approve or deny them, and read the audit log. Common builds include sync jobs, admin tooling, and agents that call SignPath APIs from your backend.

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 SignPath 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/signpath in the open repo. When SignPath 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 SignPath data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store SignPath 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 SignPath 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 9 destructive SignPath operations. You can change a link's mode at hub.corsair.dev/me.