Logto MCP Server
Enables managing Logto resources (users, applications, organizations, roles) via MCP clients like Cursor or Claude Desktop.
README
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.
Setup
npm install
npm run build
Environment variables
| Variable | Required | Description |
|---|---|---|
LOGTO_APP_ID / LOGTO_CLIENT_ID |
Yes | M2M application ID |
LOGTO_APP_SECRET / LOGTO_CLIENT_SECRET |
Yes | M2M application secret |
LOGTO_ENDPOINT / LOGTO_BASE_URL |
OSS | Self-hosted Logto base URL |
LOGTO_TENANT_ID |
Cloud | Cloud tenant ID (OSS defaults to default) |
LOGTO_API_INDICATOR |
No | OSS default: https://default.logto.app/api |
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/api
Logto 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 |
|---|---|
logto_health |
Verify M2M credentials |
list_users / get_user / create_user / update_user / delete_user |
Users |
list_applications / get_application / create_application / update_application / delete_application |
Applications |
list_organizations / get_organization / create_organization / update_organization / delete_organization |
Organizations |
list_organization_members / add_organization_members / remove_organization_member |
Organization members |
list_roles / get_role / create_role / update_role / delete_role |
Roles |
list_user_roles / assign_user_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 --watch
Logging 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.1
The workflow will:
- Build the package
- Create a GitHub Release with notes and the
.tgzartifact - Publish 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.