SDK
Your app docks in.
@locins/id is the npm package for Sign in with Locins: OAuth 2.1 with PKCE for web, React and Expo.
Three steps to your first token.
Install, initialise the client, sign in with scopes.
Public clients use PKCE, with no client secret at all. Write scopes need a confidential app with a client secret.
// 1. Installnpm install @locins/id // 2. Initialise the client with scopesimport { LocinsAuth } from '@locins/id' const auth = new LocinsAuth({ clientId: 'YOUR_CLIENT_ID', redirectUri: 'https://yourapp.com/callback', scope: ['identity', 'adventures:read'],}) // 3. Sign in (redirect flow)await auth.login() // On the callback page: exchange the code for a tokenconst result = await auth.handleCallback()The user keeps a hand on the switch.
asks for identity, adventures:read
identity ✓adventures:read ✓identityadventures:read
- Granular: one scope per data type, not per area.
- Deliberate: every scope in plain words on the consent screen.
- Revocable: access ends immediately, with nothing for you to do.
Grants live at Locins, not in the token.
An access token only says who is asking. Which scopes are granted behind it, Locins resolves anew on every access. Your app does not need to mirror permissions.
One address, one standard.
Locins speaks the Model Context Protocol. An AI client gets this address, signs in via OAuth and then sees exactly the tools for which your user has granted scopes.
https://locins.com/api/v1/mcp- Transport
- Streamable HTTP
- Protocol
- JSON-RPC
- Sign-in
- OAuth, bearer token
- Discovery
- well-known endpoints
More than 210 tools
All tools with description, inputs and required scope are listed in the manifest.
View the manifestTalk to us before you build.
No example runs without a client ID. Request your app and we set it up by hand.