Global Configuration
The LeanMCP CLI stores configuration in~/.leanmcp/config.json.
Config File Location
~/.leanmcp/config.json on Unix-like systemsC:\Users\<username>\.leanmcp\config.json on WindowsConfiguration Schema
Your LeanMCP API key (set via
leanmcp login)API endpoint URL. Defaults to
https://api.leanmcp.comAllowed values:https://api.leanmcp.com(production)https://devapi.leanmcp.com(development)https://qaapi.leanmcp.com(QA)http://localhost:3001(local testing)
ISO timestamp of last configuration update
Project Configuration
Each deployed project has a local configuration file at.leanmcp/config.json in the project directory.
Project Config Schema
Unique project identifier from LeanMCP cloud
Human-readable project name
Deployment subdomain (e.g., ‘my-app’ for my-app.leanmcp.app)
Full deployment URL (e.g., https://my-app.leanmcp.app)
ISO timestamp of last deployment
ID of the last successful build
ID of the current active deployment
Example
.leanmcp/config.json
Environment Variables
The CLI respects the following environment variables:Authentication
Override API key from config file (not recommended for production)
AWS Cognito (if using Cognito auth)
AWS region for Cognito
Cognito User Pool ID
Cognito App Client ID
Cognito App Client Secret (if using client credentials)
Auth0 (if using Auth0 auth)
Auth0 domain (e.g., ‘your-tenant.auth0.com’)
Auth0 application client ID
Auth0 application client secret
Auth0 API audience
Clerk (if using Clerk auth)
Clerk frontend API domain
Clerk secret key
TypeScript Configuration
The CLI generates projects with the following recommendedtsconfig.json:
tsconfig.json
The
experimentalDecorators and emitDecoratorMetadata options are required for using @Tool, @Authenticated, @Elicitation, and other decorators.Package.json Scripts
Generated projects include these npm scripts:package.json