What Kroy can do with your server

Kroy is the governed interface between an organisation and AI: organisations connect their systems to Kroy, their AI tools connect to Kroy, and Kroy decides, runs and records every request. The marketplace is where MCP servers enter that picture.

What Kroy does with a listed server today, and what it will do through the Kroy app, are listed separately below. The Kroy app is in early access, so the second list describes how it is designed to work, not something you can use yet.

Today, in the marketplace

• Lists it for every client. One listing, with configuration for the common MCP clients.
• Reads its tools. For remote servers, Kroy connects and shows the tools the server reports, including whether each is read-only or can change data.
• Checks it. On submission, on request, and every six hours for remote servers. What Kroy checks.
• Has a person review it. How review works.
• Collects ratings from people who tried it.
• Makes it findable by AI. Through the JSON API and the marketplace's own MCP server, an AI client can search listings for a user.

With the Kroy app (early access)

When an organisation uses Kroy, a marketplace server can be connected through Kroy instead of directly to each person's AI client. Kroy then:

• Lets the organisation approve it. Admins choose which marketplace servers their people may use, and the listing shows exactly what they are approving.
• Holds its credentials. API keys or OAuth tokens for your server are stored by Kroy and never given to the AI client.
• Decides every tool call. Each call is checked against the person, the AI acting for them, what the person has allowed, and the organisation's rules, just like every other system connected to Kroy.
• Requires approval where it matters. Organisations can require a named person to approve calls to tools that change or delete data. Your readOnlyHint and destructiveHint annotations feed straight into this, so annotate your tools accurately.
• Records every call: who, which AI, which tool, the decision and the outcome, including refused calls.
• Lets people use it from any AI. One approved connection serves Claude, ChatGPT, Copilot and the rest.

For you as a developer, this means organisations that would never let staff connect an unknown MCP server directly can adopt yours with controls around it.

Designing for it

• Give every tool one clear job, a precise description and an honest annotation.
• Separate reading from writing: list_invoices and create_invoice_draft, not invoices with a mode flag.
• Prefer drafts to irreversible actions where you can: create a draft, and let a person send it.
• Support OAuth for remote servers, so an organisation connects once and Kroy holds the token.
• Return concise results and paginate; Kroy truncates very large results and says so.
• Never ask for more data than a tool needs.

Questions about the Kroy app: hello@getkroy.com, or join the waitlist at getkroy.com/waitlist.