Open source and independently maintained
Browse the source, report an issue, or follow the project on GitHub.
Use GitHub Issues for non-security questions, documentation problems, and bug reports:
Before filing, try the latest release or current main when practical, and check:
For setup or runtime issues, include:
simplelogin-mcp version or commit.pnpm, or another wrapper.http or stdio.SL_API_KEY, MCP_AUTH_TOKEN, authorization headers, or SimpleLogin account details.app.simplelogin.io or a self-hosted SimpleLogin instance.For live smoke-test cleanup warnings, include only the affected artifact type, failed cleanup status, and whether manual cleanup was verified. Keep the run id, temporary alias/contact ids, addresses, contacts, account responses, and error details private. Inspect and clean up leftover SimpleLogin artifacts before rerunning.
Do not open a public issue for vulnerabilities, credential leaks, authentication bypasses, or exposure problems. Follow SECURITY.md and use GitHub private vulnerability reporting from the repository’s Security tab when that action is available. If it is not visible, do not publish sensitive details in an issue or discussion.
This project supports the MCP server, its SimpleLogin API integration, public documentation, Docker image, and test coverage.
Use SimpleLogin support or the SimpleLogin web UI for:
For reverse proxies, TLS, firewalls, and hosting platforms, this project can document the server’s
requirements (POST /mcp, GET /health, bearer auth, loopback defaults, and origin validation),
but it cannot provide support for every deployment stack.
Start with Troubleshooting and the FAQ before opening an issue.
Open source and independently maintained
Browse the source, report an issue, or follow the project on GitHub.