FavStash for agents

Your creative workflow, inside your agent

Connect Codex or Claude Code to your stash, social accounts, and publishing tools. The FavStash CLI signs you in, sets up a local MCP bridge, and uploads local media when you ask your agent to use it.

The npm package installs both favstash (setup and sign-in) and favstash-mcp (the bridge your agent runs). Read the CLI guide · View on npm

Choose your agent

Connect Claude Code

Use the CLI bridge, browser sign-in, and files on your computer.

prompt
Install FavStash in Claude Code by following https://www.favstash.app/INSTALL_FOR_AGENTS.md#claude-code; you may configure only the FavStash MCP connection, request permission if required, complete browser sign-in with me, and verify a read-only tool call before reporting success.

Paste this prompt into your agent to connect FavStash and sign in.

  1. Your agent installs the CLI and opens FavStash in your browser.
  2. You sign in and approve access. Your credentials stay out of the conversation.
  3. The agent adds the local bridge, checks the connection, and asks you to reload the host if needed.
Manual CLI setup

Requires Node.js 20+ and the Claude Code CLI on PATH. Run on the computer where the agent runs.

bash
npm install -g @sketric/favstash-mcp@latest
favstash auth login
favstash setup --agent claude-code
favstash doctor

Use favstash setup --agent claude-code --dry-run to preview the command.

Remote OAuth alternative
  1. Run this command to add FavStash directly as a remote MCP connection.
  2. In Claude Code run /mcp, choose FavStash and authenticate. Complete browser sign-in and reload the tools.
bash
claude mcp add --transport http --scope user favstash https://mcp.favstash.app/mcp

Remote MCP uses HTTPS media URLs. The local bridge also uploads files from your computer.

Verify the connection

prompt
Use FavStash's get_stash_summary tool once with no filters. Report whether it succeeded and the returned counts. Zero counts are valid. Do not modify any data.

A successful response can include zero counts. Browser approval, configuration, or tool discovery alone does not verify access to your account.

API keys and troubleshooting

OAuth is the default. For unattended jobs or hosts without OAuth, create a scoped API key in AI Connect and store it as FAVSTASH_API_KEY in your local secret environment. Never paste tokens into a chat or commit them.

Use favstash auth status to inspect local sign-in, favstash doctor to check remote compatibility, and favstash auth logout to revoke the CLI session. An API key in the environment takes precedence over OAuth.

If sign-in is approved but the agent reports an initialization or protocol error, save the error and your client version for support. Repeating sign-in may not fix a server compatibility issue. Verify a read after reconnecting before calling the setup complete.

OAuth credentials use the OS credential store. On a private machine without a usable keychain, explicitly choose favstash auth login --credential-store file. For SSH, containers, and cloud tasks, the browser must be able to reach the CLI’s loopback callback; otherwise use the host’s remote OAuth support or a securely supplied API key.

Update with npm install -g @sketric/favstash-mcp@latest, then restart the agent. A remote MCP connection cannot read arbitrary paths on your computer.

Agent installation guideCLI referenceAPI reference