Checks API health, lists organization certificates and projects, and reads the signing policies the connected user can submit against.
5actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves all certificates available for code signing in the organization. Development teams find the right certificate without searching external tools.
Ayro fetches signing policy requirements for code signing operations. Engineers understand approval workflows before submitting code for signature.
Ayro lists all projects in the SignPath organization. Teams identify which projects can use signing automation for their release pipeline.
Each card is one request a support team gets, and the Signpath actions Ayro runs to close it.
When a signing step fails, Ayro 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.
Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Signpath actions it has and picks the ones a request needs.
Authorize the Signpath account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Signpath actions that close it and chains as many as the request needs.
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 freeSignpath · Ayro
What can you do in Signpath without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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.
All 5 actions your agent can call on Signpath, straight from the live MCP connection.
Check if the SignPath API is healthy and operational.
Retrieve all certificates available in a SignPath organization.
List all projects for an organization.
Retrieve signing policy details for code signing operations.
Retrieves SignPath system information including the application version and the web UI base URL.
Same connection, same setup. Pick the next one your team already uses.
Searches code across a workspace, opens branches and pull requests, comments and merges after review, and reports which pipeline run broke.
Looks up current Context7 MCP documentation and triggers updates without leaving the conversation.
Answers Gitea configuration questions from the running instance and renders Markdown or AsciiDoc into the HTML Gitea itself would produce.
Reports connection and sync health, issues connect and reconnect sessions, triggers one-off syncs, and proxies authenticated provider calls.
Reports Sauce Labs status, pulls test job history, and confirms supported platforms, tunnel versions, and Appium end-of-life dates.
Reads back every configured check with its status and settings, and returns the current monitoring node list with IPv4 and IPv6 addresses.

Authorize the account and your agent has all 5 actions from the first conversation.
