Local stdio
Local stdio is the smallest trust boundary: the MCP client launches the compiled server and communicates over its standard input and output streams. No network listener is opened.
{ "mcpServers": { "simplelogin": { "command": "node", "args": ["/absolute/path/to/simplelogin-mcp/dist/index.js"], "env": { "TRANSPORT": "stdio", "SL_API_KEY": "sl-your-key-here" } } }}This JSON illustrates Claude Desktop's stdio shape; other clients use different configuration formats. Run pnpm install --filter simplelogin-mcp --frozen-lockfile && pnpm build first. Stdio does not use MCP_AUTH_TOKEN; keep the client config private because it contains your API key. Use the recipe for your MCP client.
Configure a client
Section titled “Configure a client”-
Get and build the server. Clone the project if you do not already have a checkout, then build it:
Terminal window git clone https://github.com/enthouan/simplelogin-mcp.gitcd simplelogin-mcpcorepack enablepnpm install --filter simplelogin-mcp --frozen-lockfilepnpm build -
Use an absolute entry path. Point the client at this checkout’s
dist/index.js. -
Set the transport and key. Create a dedicated key, then pass
TRANSPORT=stdioandSL_API_KEYin the client process environment. -
Restart the client. Reopen it so the process configuration is reloaded.
The server writes diagnostics to stderr because stdout is reserved for MCP messages.
Verify through MCP
Section titled “Verify through MCP”After the client reports that simplelogin-mcp is connected and its tools are discovered, verify a
read-only account call.
Verify it works
After the client discovers the server, use this low-data, read-only check:
Can you show me my SimpleLogin account usage?Use Operations when upgrading or rolling back the source checkout used by this client configuration.