Returns the SP-initiated SSO sign-on URL, lists company identifiers, and completes the SAML round trip for account access.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro lists all companies configured in HackerRank Work with their identifiers. Supporters can verify which organizations are active without accessing the admin console.
Each card is one request a support team gets, and the HackerRank Work actions Ayro runs to close it.
Ayro identifies which company the person belongs to and returns the SP-initiated SSO sign-on URL for it, so a stalled login is unblocked in the conversation rather than by an IT ticket.
Ayro lists every company on the account with its unique identifier, which is the value an SSO metadata lookup needs and the fastest way to settle a question about which tenant someone is on.
When the identity provider posts a SAMLResponse and RelayState, Ayro consumes the assertion to finish the sign-in rather than leaving the user staring at a half-finished redirect.
Ayro gathers the company identifier and the sign-on URL first, so if the issue does turn out to need a human, the ticket arrives with the SSO facts already attached.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the HackerRank Work actions it has and picks the ones a request needs.
Authorize the HackerRank Work 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 HackerRank Work 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 freeHackerRank Work · Ayro
What can you do in HackerRank Work 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 HackerRank Work.
No. This toolkit exposes three actions - List Companies, Get SSO Sign-On URL, and Consume SAML Assertion - and all three are about single sign-on. Scheduling coding interviews, generating assessments, and reviewing submissions are not in the action list, so Ayro cannot do them through this integration.
All 3 actions your agent can call on HackerRank Work, straight from the live MCP connection.
List all companies and their unique identifiers.
Consume SAML assertions.
Get the SP-initiated SSO sign-on URL.
Same connection, same setup. Pick the next one your team already uses.
Checks channel presence, publishes realtime and batch messages, sends push notifications, and maintains the Ably device registry.
Reads Bubble records by ID, creates them singly or in bulk, triggers your backend API workflows, and patches or deletes records that are wrong.
Reports what deployed and what is queued, summarises what a release contains, aborts a bad deployment, and stands new projects up against their servers.
Searches Hacker News discussions, resolves ranked story IDs into readable items, and reads Ask HN, Show HN, job, and user feeds.
Lists virtual machines, snapshots, locations and resource pools, pulls billing accounts and invoices, and updates the user profile.
Checks API health, lists organization certificates and projects, and reads the signing policies the connected user can submit against.

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