Logto FAQs

Question 1

Which Logto APIs does it support?

Accepted Answer

It supports the comprehensive Logto Management API, covering aspects like users, applications, organizations, roles, SSO, webhooks, and more, with over 120 tools. It also offers optional support for the Logto Accounts API for end-user self-service tools.

Question 2

How does Logto MCP Server handle API authentication?

Accepted Answer

For the Management API, it includes auto-refreshing Machine-to-Machine (M2M) token management, eliminating the need for manual token rotation. For the Accounts API, it uses an end-user bearer token for context-specific operations.

Question 3

Is Logto MCP Server suitable for self-hosted Logto deployments?

Accepted Answer

Yes, it is explicitly built for and optimized to integrate with self-hosted Logto instances, providing a powerful interface for managing your identity and access management solution.

Question 4

What is Logto MCP Server?

Accepted Answer

Logto MCP Server is a fully-featured Model Context Protocol (MCP) server that exposes the complete Logto Management API and Accounts API as MCP tools, specifically designed for self-hosted Logto instances.

Question 5

What clients are compatible with Logto MCP Server?

Accepted Answer

Logto MCP Server is built to work seamlessly with Claude Desktop, Claude Code, and any other client that supports the Model Context Protocol (MCP), providing a flexible integration experience.

Logto

Logto

主要功能

使用案例

主要功能

使用案例