LStack exposes a Model Context Protocol (MCP) surface for supported clients and workers. MCP tools let an authorized client interact with LStack projects, tickets, documentation, execution workflows, and runtime operations without bypassing the product’s access rules.
Connection details
The dashboard provides the connection URL, authentication token, and client-oriented configuration for available MCP surfaces. Tokens are credentials and must not be committed to a repository or included in support material.
The tools visible to a client depend on its role and authorization. LStack scopes tool access so that worker execution, operator actions, and project context do not automatically share the same permissions.
Treat every MCP token as a secret. Rotate it if it is exposed, and never paste it into public documentation or issue reports.
Where to continue
This section is the foundation for future client setup guides and the generated MCP tool catalog. Each guide should identify the client, authentication flow, tool scope, and tested LStack version. 
