Connect a local MCP client
Opt-in loopback server, per-client approval and independent scopes.
Connect and approve a client
Section titled “Connect and approve a client”- Open Settings → Intelligence → MCP & AI Tools and enable Enable local MCP server.
- Use Connect AI Tool… to view available setup snippets. The bundled
Contents/Helpers/StashMCPbridge uses stdio and connects to the loopback server at127.0.0.1:47841. - Start the client and approve its request in Stash. Grant only what you need. History reads, Pinboard reads and writes are separate permissions.
Access is device-local and uses a per-client token stored in Keychain. Keep tokens out of public issue reports and command output. An approved external tool can process data it reads according to its own settings. Check those settings before granting read access.
Remove or troubleshoot access
Section titled “Remove or troubleshoot access”Use Remove access for the client or turn off the local server. If an old bridge credential is preventing a new approval prompt, use the bridge’s --reset option for that client. Check the selected scopes and whether Stash is running. Interoperability with each client version requires its own validation.