Connect Signpath to Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini, GitHub Copilot and any other MCP client, for your whole team. Metorial adds security, governance, and tracing, and gives everyone one Magic MCP URL to connect.
Ask your agent in plain language. Each of these maps to a real tool on the server.
Use the get certificate tool in Signpath
Use the get signing request tool in Signpath
Use the get project tool in Signpath
Use the approve or deny signing request tool in Signpath
Use the resubmit signing request tool in Signpath
Use the get signing policies tool in Signpath
Supported Tools
get_certificate
Get Certificate
Retrieve detailed metadata for a specific certificate by its slug, or retrieve the certificate associated with a specific project's signing policy. Use certificateSlug for direct lookup, or projectSlug + signingPolicySlug to get the certificate linked to a signing policy.
get_signing_request
Get Signing Request
Retrieve the status and details of a signing request by its ID. Returns the current status, project info, signing policy info, artifact links, origin data, and parameters. Use this to check whether a signing request has completed, is waiting for approval, or has failed.
get_project
Get Project
Retrieve detailed information about a specific project by its slug. Returns the project's signing policies, artifact configurations, and other settings.
approve_deny_signing_request
Approve or Deny Signing Request
Approve or deny a signing request that is waiting for approval. This is typically used for release-signing workflows that require manual approval before processing. The signing request must be in the **WaitingForApproval** status.
resubmit_signing_request
Resubmit Signing Request
Resubmit an existing signing request with a different signing policy. Useful for release candidates where you want to postpone the release decision. Origin verification is evaluated based on the original request's origin data, preserving integrity even when fully detached from the build process.
get_signing_policies
Get Signing Policies
Retrieve signing policy information including the associated X.509 certificate and RSA key parameters. Filter by project and/or signing policy slug. If no filters are provided, returns all signing policies where the authenticated user is assigned as Submitter.
submit_signing_request
Submit Signing Request
Submit a new code signing request to SignPath. Provide an artifact file as Base64, its filename, the project, and signing policy. Fast requests use hashSigningData and return a downloadable signature result immediately. User-defined parameters can be passed as key-value pairs.
list_projects
List Projects
List all projects in the organization. Returns project summaries and signing policies. Use get_project for artifact configurations and complete project details. Use this to discover available projects and their slugs for signing request submission.
get_audit_log
Get Audit Log
Retrieve audit log events from SignPath. Choose between general events (administrative changes to users, certificates, projects, signing policies, artifact configurations) or signing request events specifically. Returns one page of events; pass the nextCursor to retrieve the following page. This API is in preview.
list_certificates
List Certificates
List all certificates in the organization. Returns certificate names and active status. Use get_certificate to retrieve the X.509 thumbprint and validity details.
get_signing_request_status
Get Signing Request Status
Poll signing progress using the status endpoint. Returns the current status, workflow stage, and whether processing has finished.
get_current_user
Get Current User
Retrieve the authenticated SignPath user, including CI users, their role, and account status.
download_signed_artifact
Download Signed Artifact
Prepare the signed artifact from a completed signing request for download. The authenticated user must have permission to access the request.
Enable Signpath in Metorial. In your Metorial portal, enable the Signpath MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
Add a custom connector. Open Customize, then Connectors. Select Add, then Custom, then Web.
Paste your Metorial MCP URL. Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>) and continue.
Sign in. Select Add and sign in to load Signpath tools.
Enable Signpath in Metorial. In your Metorial portal, enable the Signpath MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
Add a custom MCP server. On ChatGPT web, open Plugins, select +, then Add custom MCP server.
Paste your Metorial MCP URL. Name it Metorial, paste your Magic MCP URL (<your-magic-mcp-url>), choose OAuth and accept the risk notice.
Create and install the plugin. Select Create as a plugin, install it and sign in to load Signpath tools.
Enable Signpath in Metorial. In your Metorial portal, enable the Signpath MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
Add Metorial to your MCP config. Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
Sign in. Open Customize in the sidebar, find Metorial and sign in to load Signpath tools.
{
"mcpServers":{
"metorial":{
"url":"<your-magic-mcp-url>"
}
}
}
Enable Signpath in Metorial. In your Metorial portal, enable the Signpath MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
Add the server over HTTP. Add --scope user to use it in every project.
Sign in. Run /mcp, select Metorial and sign in to load Signpath tools.
claude mcp add --transport http metorial <your-magic-mcp-url>
Enable Signpath in Metorial. In your Metorial portal, enable the Signpath MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
Add the server and sign in. The Codex CLI, IDE extension and ChatGPT desktop app share this config.
Check the connection. Type /mcp in Codex to see Metorial and its Signpath tools.
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
Run Signpath through the Metorial gateway
One governed layer for every app your agents reach, not a separate connector per tool.
Give Signpath and every other app to your whole team through one MCP gateway, behind your SSO.
Scope which teams and agents can use Signpath tools with role-based access control, and trace every call.
Prefer to run it yourself? Metorial is open source and self-hostable.
Submit artifact or hash signing requests, approve or deny requests, resubmit completed requests, poll progress, and download signed artifacts. Discover projects, signing policies, and certificate details; read audit logs and inspect the authenticated user.
Frequently asked questions
Common questions about connecting Signpath to AI agents with Metorial.
How many tools does the Signpath MCP server have?
The Signpath MCP server exposes 13 tools, including Get Certificate, Get Signing Request, Get Project. Each one is governed and traced through Metorial.
Does the Signpath MCP server support triggers?
Signpath exposes tools your agents call on demand; it does not publish event triggers yet. Everything still runs through one governed MCP URL.
Which AI clients can use the Signpath MCP server?
Any MCP client, including VS Code, Windsurf, Zed, OpenCode and Grok. Each one reaches the Signpath MCP server through the same Metorial URL.
How do I give only some teams access to Signpath?
Use role-based access control to decide which teams, users, and agents can use Signpath and which of its tools they can call.
Can I self-host the Signpath MCP server?
Yes. Metorial is open source, so you can run the Signpath MCP server yourself or use the hosted gateway.
Connect Signpath to production AI agents
See how Metorial gives your team governed access to Signpath, with tracing and security controls built in.