Can Lyro submit a signing request or sign an artifact through SignPath?

No. The connected actions - Get Health Check, List Certificates, List Projects, Retrieve Signing Policy Details, and Retrieve System Info - are all retrieval calls. Submission stays in your CI/CD pipeline, which is where SignPath expects it to happen.

Which signing policies can Lyro see?

Retrieve Signing Policy Details returns, when no filter is applied, the policies where the authenticated user is assigned as Submitter. The answer is therefore scoped to the credential you connect rather than every policy in the organization.

Does Lyro need our organization ID before it can look anything up?

Yes for the certificate and project lookups. List Certificates requires a valid organization_id taken from your SignPath account settings, and List Projects is run once that ID is confirmed, so each lookup is bound to one organization.

What does Lyro do when SignPath itself is unavailable?

Get Health Check verifies API availability before other operations, so Lyro reports an outage rather than returning an empty certificate list that looks like a permissions problem. If the release is blocked, it hands off to a human agent with the conversation history intact.

Signpath MCP integration

Checks API health, lists organization certificates and projects, and reads the signing policies the connected user can submit against.

Connect Signpath See all integrations

5actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

List certificates
Lyro retrieves all certificates available for code signing in the organization. Development teams find the right certificate without searching external tools.
Retrieve signing policy details
Lyro fetches signing policy requirements for code signing operations. Engineers understand approval workflows before submitting code for signature.
List projects
Lyro lists all projects in the SignPath organization. Teams identify which projects can use signing automation for their release pipeline.

See all 5 actions

How businesses use Signpath + Lyro

Each card is one request a support team gets, and the Signpath actions Lyro runs to close it.

Rule out a SignPath outage before anyone debugs the pipeline
When a signing step fails, Lyro checks whether the SignPath API is healthy and reports the installed version and web UI address, so the team knows within a message whether the problem is theirs.
Get Health CheckRetrieve System InfoList Projects
Answer which certificate a release will be signed with
Lyro lists the certificates available in the organization and the policy metadata attached to them, so a developer hunting for a certificate ID gets it without an admin opening the console.
List CertificatesRetrieve Signing Policy DetailsList Projects
Explain what a signing policy actually allows
Lyro reads the signing policy details behind a request, including certificate information and RSA key parameters, turning a vague approval question into a specific answer about what that policy covers.
Retrieve Signing Policy DetailsList CertificatesGet Health Check
Point a new engineer at the right project
Lyro paginates the organization's projects and matches the one the engineer describes, so onboarding questions about where a build should submit its artifacts stop landing on the release owner.
List ProjectsList CertificatesRetrieve System Info

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Signpath actions it has and picks the ones a request needs.

01
Connect Signpath
Authorize the Signpath account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Signpath actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Signpath · Lyro

Everything else about Signpath

Setup, permissions, and the limits of what Lyro can do inside Signpath.

No. The connected actions - Get Health Check, List Certificates, List Projects, Retrieve Signing Policy Details, and Retrieve System Info - are all retrieval calls. Submission stays in your CI/CD pipeline, which is where SignPath expects it to happen.

Every action available in Signpath

All 5 actions your agent can call on Signpath, straight from the live MCP connection.

Get health check
Check if the SignPath API is healthy and operational.
List certificates
Retrieve all certificates available in a SignPath organization.
List projects
List all projects for an organization.
Retrieve signing policy details
Retrieve signing policy details for code signing operations.
Retrieve system info
Retrieves SignPath system information including the application version and the web UI base URL.