Logto MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Logto MCP Serverlist all users"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Logto MCP Server
A Model Context Protocol server that exposes the Logto Management API to MCP clients (Cursor, Claude Desktop, etc.).
Built with:
@modelcontextprotocol/sdk(stdio transport)@logto/apiManagement SDK
Prerequisites
A Logto instance (self-hosted OSS or Cloud)
A Machine-to-machine application in Console → Applications
An M2M role that includes Logto Management API permissions (
all)
See Interact with Management API for details.
Related MCP server: @willpowell8/cursor-cloud-agent-mcp
Setup
npm install
npm run buildEnvironment variables
Variable | Required | Description |
| Yes | M2M application ID |
| Yes | M2M application secret |
| OSS | Self-hosted Logto base URL |
| Cloud | Cloud tenant ID (OSS defaults to |
| No | OSS default: |
Copy .env.example as a reference. For MCP clients, pass variables in the env block (below).
Self-hosted / OSS
LOGTO_ENDPOINT=https://your.logto.endpoint
LOGTO_APP_ID=...
LOGTO_APP_SECRET=...
# Optional: LOGTO_TENANT_ID=default
# Optional: LOGTO_API_INDICATOR=https://default.logto.app/apiLogto Cloud
LOGTO_TENANT_ID=your-tenant-id
LOGTO_APP_ID=...
LOGTO_APP_SECRET=...Cursor / Claude Desktop / MetaMCP config
Local build:
{
"mcpServers": {
"logto": {
"command": "node",
"args": ["C:/Users/rascal/projects/logto-mcp/build/index.js"],
"env": {
"LOGTO_ENDPOINT": "https://your.logto.endpoint",
"LOGTO_APP_ID": "your-m2m-app-id",
"LOGTO_APP_SECRET": "your-m2m-app-secret"
}
}
}
}From GitHub repo (no package registry auth):
{
"mcpServers": {
"logto": {
"command": "npx",
"args": ["-y", "github:KDunin/logto-mcp"],
"env": {
"LOGTO_ENDPOINT": "https://your.logto.endpoint",
"LOGTO_APP_ID": "your-m2m-app-id",
"LOGTO_APP_SECRET": "your-m2m-app-secret"
}
}
}
}From GitHub Packages (after a release is published):
# once in ~/.npmrc (needs a PAT with read:packages)
echo "@kdunin:registry=https://npm.pkg.github.com" >> ~/.npmrc
echo "//npm.pkg.github.com/:_authToken=YOUR_GH_PAT" >> ~/.npmrc{
"mcpServers": {
"logto": {
"command": "npx",
"args": ["-y", "@kdunin/logto-mcp"],
"env": {
"LOGTO_ENDPOINT": "https://your.logto.endpoint",
"LOGTO_APP_ID": "your-m2m-app-id",
"LOGTO_APP_SECRET": "your-m2m-app-secret"
}
}
}
}Use an absolute path to build/index.js for local runs. After changing env or rebuilding, restart the MCP client.
Tools
Tool | Description |
| Verify M2M credentials |
| Users |
| Applications |
| Organizations |
| Organization members |
| Roles |
| User ↔ role assignment |
Development
npm run build # compile TypeScript to build/
npm start # run stdio server (expects MCP client on stdin)
npm run dev # tsc --watchLogging goes to stderr only so stdout stays reserved for MCP JSON-RPC.
Releasing
Releases are automated by .github/workflows/release.yml when you push a version tag.
Bump
versioninpackage.json(must match the tag without thevprefix).Commit, then tag and push:
git tag v1.0.1
git push origin v1.0.1The workflow will:
Build the package
Create a GitHub Release with notes and the
.tgzartifactPublish to GitHub Packages as
@kdunin/logto-mcp(stable tags only; usesGITHUB_TOKEN, no npmjs login)
ENEEDAUTH against registry.npmjs.org means you were targeting the public npm registry. This project publishes to https://npm.pkg.github.com instead.
Prerelease tags like v1.0.1-beta.1 create a GitHub prerelease and skip package publish.
License
MIT
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KDunin/logto-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server