yutori-ai/yutori-mcp
Overview
This skill logs you into Yutori and saves the API key so Yutori tools can run automatically. It provides a simple, secure authentication flow that opens a browser for OAuth-style sign-in and stores credentials locally. Use it as the single-step entry point to connect your account to Yutori services.
How this skill works
Run a one-time command in a separate real terminal: it opens your default browser, completes interactive authentication, and runs a local callback server to receive the token. On success the skill writes the API key to ~/.yutori/config.json. After that, all Yutori tools detect the saved credentials and operate without additional manual sign-in.
When to use it
- First-time setup of Yutori tools on a new machine
- Re-authenticating after credential expiry or rotation
- Setting up a development workstation to run agentic workflows
- Preparing an environment where Yutori agents will run unattended
Best practices
- Run the login command in a full terminal (not inside an automated shell or restricted environment)
- Use a separate terminal window so the browser and local callback can interact with a live TTY
- Verify ~/.yutori/config.json permissions and keep the file private
- Re-run the login command if you see authentication errors or if tokens expire
- Do not attempt to run the login command inside non-interactive CI jobs; use service credentials appropriate for CI
Example use cases
- Initial onboarding: run the command to link your account and unlock Yutori agent capabilities
- Developer laptop setup: authenticate once so local dev tools and scripts can call the API
- Troubleshooting: re-authenticate to refresh tokens after permission changes
- Local demos: authenticate before running demos that require live account access
FAQ
Open a separate terminal and run: uvx yutori-mcp login
Where are credentials stored?
The API key is saved to ~/.yutori/config.json on successful login.
Can I run this inside a script or CI job?
No. The login flow needs an interactive terminal and a browser callback. For CI, use service keys or other non-interactive auth methods.