<!-- Generated by scripts/generate-agent-docs.mjs. Edit the generator or agentConnectionData.ts. -->

# FavStash remote MCP

Use remote MCP for Claude Chat, Desktop / Cowork and ChatGPT custom apps. It also works as an alternative for local agents that do not need filesystem uploads. OAuth is the default; no FavStash API key needs to be pasted into chat.

These URLs are runtime endpoints, not documentation pages:

| Client | Streamable HTTP endpoint |
| --- | --- |
| Claude and general MCP hosts | https://mcp.favstash.app/mcp |
| ChatGPT custom app | https://mcp.favstash.app/chatgpt/mcp |

## chatgpt

ChatGPT.

FavStash’s ChatGPT directory listing is pending. Custom MCP setup requires Developer mode and the appropriate plan / workspace permissions; menu labels vary by client.

[Open ChatGPT settings](https://chatgpt.com/#settings/Connectors)

1. Open ChatGPT Settings → Apps (or Plugins) and enable Developer mode where available. Choose Create / Add a custom app.
2. Name it FavStash, paste the ChatGPT server URL below, and choose OAuth. Keep discovered settings; no client ID or secret needs to be copied.
3. Sign in with FavStash, approve access, enable the app in your conversation, and run the verification prompt below.

```text
https://mcp.favstash.app/chatgpt/mcp
```

## claude-hosted

Claude.

Custom connector for Claude Chat and supported Desktop / Cowork accounts. Workspace policy may require an administrator. FavStash is not listed in Claude’s connector directory.

[Open Claude settings](https://claude.ai/customize/connectors)

1. Open Customize → Connectors → Add custom connector. Name it FavStash and paste the server URL below. Leave advanced OAuth client ID and secret blank.
2. Select Connect, sign in to FavStash in your browser, and approve the requested access.
3. Enable FavStash in the conversation and run the verification prompt below.

```text
https://mcp.favstash.app/mcp
```

## claude-code

Claude Code — remote alternative; prefer the [CLI](https://www.favstash.app/cli.md) for local media.


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.

```text
https://mcp.favstash.app/mcp
```

```sh
claude mcp add --transport http --scope user favstash https://mcp.favstash.app/mcp
```

## other-cli

Other agents.

For Cursor, Windsurf, Hermes, OpenClaw, and other MCP clients. Support and settings depend on the installed host version.

1. Open your host’s MCP settings and add a Streamable HTTP server named favstash using the URL below. Keep other server entries intact.
2. Choose Connect / Authenticate and complete FavStash OAuth in your browser. Check the host’s current help for its exact configuration format.
3. Reload the host, discover the tools, and run the verification prompt below. If the host cannot use remote OAuth, use the API key fallback.

```text
https://mcp.favstash.app/mcp
```

## muse

Muse.

Custom connector preview for Meta’s Muse personal assistant. Browser OAuth with FavStash has not yet been verified in Muse.

1. Paste the setup prompt into a Muse conversation. Ask Muse to create a custom connector using FavStash’s remote MCP endpoint.
2. Complete browser sign-in if Muse offers it for the custom connector. Otherwise create a scoped API key in FavStash AI Connect and enter it only through Muse’s secure credential prompt.
3. Let Muse verify one read-only stash summary, then save the working connector for future conversations. This is the personal assistant, not Muse Code; no Muse Code terminal commands are needed.

```text
https://mcp.favstash.app/mcp
```

```text
Create a FavStash custom connector in Meta Muse by following https://www.favstash.app/INSTALL_FOR_AGENTS.md#muse. Use the remote Streamable HTTP MCP endpoint https://mcp.favstash.app/mcp. Configure only FavStash. If your custom connector supports browser OAuth, let me sign in and approve access; otherwise ask me to add a scoped FavStash API key through your secure credential prompt, never in chat. Do not install or use Muse Code commands. Initialize the MCP connection, discover tools, and call get_stash_summary once with no filters. Report success only after that read returns; zero counts are valid. Do not modify or publish content. Save the verified connector for reuse.
```

[Provider guidance](https://research.meta.ai/blog/security-and-safety-for-ai-agents-our-approach-with-muse)

## codex

Codex — remote alternative; prefer the [CLI](https://www.favstash.app/cli.md) for local media.


1. Run these commands to add FavStash directly as a remote MCP connection.
2. Complete browser sign-in, reload Codex, and verify the tools in a new session.

```text
https://mcp.favstash.app/mcp
```

```sh
codex mcp add favstash --url https://mcp.favstash.app/mcp
codex mcp login favstash
```

Optional icon: [256×256 FavStash PNG](https://www.favstash.app/favstash-connector-icon.png). If the form has no icon field, continue without it.

## Verify and manage access

```text
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.
```

Approve sign-in and consent in the host/browser yourself. A conversational agent cannot guarantee that the host exposes a connector-install action. If it cannot do the host step, it should link these instructions and describe setup as pending. A successful empty result verifies access; a copied URL, health response, or tool list does not.

Manage newly authorized apps in [AI Connect](https://www.favstash.app/dashboard/connect). Older grants appear after token refresh or sign-in. Revocation blocks subsequent MCP calls and refresh; a cached REST authorization may remain usable for up to five minutes. Remove the connector in the host as well if you no longer want it listed there. API keys are separate.

## Approved sign-in, but connection failed

OAuth authorization and MCP initialization are separate steps. If a host reports a JSON-RPC deserialization or initialization error after consent, preserve the error, client version, endpoint, and time for support; omit credentials. Do not repeatedly reauthorize or claim the account is connected. Check the installed client version and, for CLI 0.4.0+, run `favstash doctor`. After a compatibility fix is deployed, reconnect or reload the host and verify one `get_stash_summary` call. Reauthorize only if the client reports an expired or rejected credential.

A custom client must send `initialize`, then `notifications/initialized` (no ID; expect HTTP 202 and an empty body), then discover tools. HTTP 200 with a JSON-RPC null-ID success response to a notification is a server protocol error, even if a permissive client ignores it.

## API key fallback

For a client without remote OAuth support, create a scoped key in AI Connect and supply `Authorization: Bearer <key>` through that client’s private secret settings. The generic `/mcp` endpoint accepts this fallback; the ChatGPT adapter is OAuth-only. Never ask a user to paste the key into a conversation.

Remote MCP cannot read an arbitrary local path. Use an HTTPS source for media or the [local CLI bridge](https://www.favstash.app/cli.md).