Limy helps brands turn AI search into a measurable growth channel for pipeline, customers, and revenue, and lets its users query that data from AI assistants like Claude and ChatGPT. Here’s how building on Descope from day one gave Limy a single identity model for both users and agents, with MCP auth in production in under a week.
About Limy
Limy addresses the reality that AI agents are becoming the new interface between brands and their customers, a shift known as business-to-agent (B2A). When a prospect asks an AI assistant for a recommendation, the assistant decides which brands are shown, in ways traditional search engine optimization (SEO) tooling wasn't built to measure. Limy helps brands understand how they appear in AI search, identify and prioritize the improvements that matter most, and measure the business impact of those changes.
The Limy platform shows brands how agents like ChatGPT, Claude, Gemini, and Perplexity crawl their sites and cite their content, and uses those insights to guide improvements. It then connects AI search visits to tracked actions and conversions, including pipeline and revenue where supported. Limy’s customers are enterprise brands and the agencies that manage several brands at once. A single Limy user may work across many different accounts for companies that may even compete with each other. Keeping each brand’s data isolated is fundamental to the product, especially within the Model Context Protocol (MCP) server that allows users to query Limy from their own AI clients.
The challenge of choosing identity on day one
Limy chose Descope just as they were bringing their product to market, with two requirements clear at the outset:
Each customer organization would get its own discrete account, with firm boundaries between each
The Limy MCP server would eventually let users authorize AI agents to act on their behalf, so the same boundaries would have to hold for agents, too
While Descope’s Free Forever Plan provides 10 monthly active tenants free of charge, Limy needed larger-scale multi-tenancy at a startup-friendly price. Descope’s Startup Program was the perfect fit: one year of the Pro tier, free of charge, while Limy built their customer base. Limy stuck with Descope and moved to a paid plan, and then clients began asking for single sign-on (SSO).
Arad Gonen, Software and DevOps Engineer at Limy, said:
"We're starting to explore SSO because our new enterprise customers require it, and Descope makes that really easy. You get a self-service link you can send to a client, they configure SAML on their own, and it simply works. I've worked with other auth providers in the past, and it wasn't that easy."
The Descope experience
Limy had the first login flow working within a couple of days, built from Descope’s SDK, docs, and tutorials without any hands-on help. Limy went passwordless from the start, so users sign in with a magic link, one-time password (OTP), or Google account via social login. That leaves Limy with zero passwords to store or reset, and it gives their users one less password to worry about. Descope issues the session tokens behind Limy’s web app and secures access to the Limy API.
Each Limy client is its own Descope tenant with its own users, with a role-based authorization (RBAC) policy applied inside each one. Descope’s prebuilt admin widgets handle tenant user management out of the box, and (after experimenting with the prebuilt options) Limy used the Descope SDK to build the same experience in its own design language.
Read more: Choosing the Right Descope UI Integration Option
With user login and multi-tenancy configured with Descope, the next step was securing the Limy MCP server. The Agentic Identity Hub allows Limy to point Descope at its MCP server’s URL and metadata, and Descope acts as the OAuth authorization server required by the MCP auth specification. The authentication piece took the Limy team roughly half an hour, and (after a two-day proof of concept period and a couple more days of tuning), the MCP server was in production in under a week.
Arad Gonen, Software and DevOps Engineer at Limy, said:
"It was really a no-brainer to use Descope’s agentic identity features. We configured the authentication part of our MCP server with Descope, and it was just 30 minutes before it was working.”
Because an agent gets its access through the user who authorizes it, the boundaries Limy set for humans extend to the agents acting for them. A marketer who connects Claude is redirected to Descope to sign in, and the accounts that user can access carry through the MCP server into Limy’s API. An agent can reach the accounts its user can access, and it can’t touch anything in another brand’s account. The Limy MCP server is read-only for now; making each user’s full per-tenant roles available through it, along with write actions, is next.
AI clients register using Client ID Metadata Documents (CIMD), the approach the MCP spec now favors, in which each client identifies itself with a URL pointing to metadata it publishes. Nobody has to create credentials by hand before connecting, and because Descope supports CIMD alongside Dynamic Client Registration (DCR) and pre-registration, Limy can accommodate clients with legacy requirements.
Room to grow, minus the paywalls
Whenever Limy has needed a new identity capability, whether it’s enterprise enablers like SSO or core AI scaffolding like MCP auth, their team found it already available in Descope without a premium markup. Building on this comprehensive foundation has given Limy:
MCP auth in production at startup speed: Configuring authentication took half an hour, and the rest came within a few more days. MCP was always a part of Limy’s vision, and Descope is how they handle MCP identity orchestration.
One set of boundaries for both users and agents: Users are bound by the tenant they’re logged in to and the role they have; agents are scoped to the user’s account, so Limy never has to design a separate access model for them.
Self-service SSO for clients that need it: As Limy prepares SSO for its first clients, they look forward to using the SSO Setup Suite. This powerful self-service workflow lets Limy’s tenants configure their own SSO connections, allowing the Limy team to focus on core engineering priorities.
Arad Gonen, Software and DevOps Engineer at Limy, said:
"Overall, the experience with Descope has been one of the best I've had with any SaaS platform. Everything is available, and you can grow with your plan. You don't need to talk to sales to enable SSO or add more tenants. It just works."
The next steps for Limy are adding write actions to the MCP server, bringing more agentic features into the platform. Descope will handle authorization for the agents that arrive, shaping their paths even as static roles evolve into fine-grained relationships, with first-class agentic identities governed by the same boundaries as their human users.
Descope is a flexible drag & drop customer and agentic identity platform that helps organizations easily add authentication, authorization, and identity management to their apps, AI agents, and MCP servers. Customers use us for initiatives such as passwordless authentication, SSO, identity federation, strong MFA, fraud prevention, and agentic identity.
To get started with Descope, sign up for a Free Forever account. If you have questions about our platform, book time with our auth experts.
