Salesforce MCP Auto Auth Chrome — Development skill for Claude Code
Fastest to Enable Salesforce MCP server for Claude Desktop with automatic session refresh from your Chrome browser — no External App needed.
How to install Salesforce MCP Auto Auth Chrome
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open kugamon/salesforce-mcp-auto-auth-chrome and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Salesforce MCP Auto Auth Chrome does
Fastest to Enable Salesforce MCP server for Claude Desktop with automatic session refresh from your Chrome browser — no External App needed.
Alternatives in Development
- Screenshot — Capture desktop, app windows, or pixel regions across OS platforms 14.6k ★
- Claude Desktop Debian — Unofficial Claude desktop app for Debian/Linux 2.5k ★
- Gmail AutoAuth MCP Installation Guide — This guide will help you install and configure the Gmail AutoAuth MCP server for managing Gmail operations thr 1.1k ★
README
Salesforce MCP Server — Auto-Auth From Chrome
[](https://pypi.org/project/salesforce-mcp-auto-auth-chrome/) [](LICENSE) [](https://www.python.org/downloads/) [](#)
A local MCP server that exposes **14 Salesforce tools** (SOQL, SOSL, CRUD, Apex execute, tooling API, REST) inside Claude Desktop — and **auto-refreshes the session from your Chrome browser** so you never have to paste a token into your config again. Wraps [`mcp-salesforce-connector`](https://pypi.org/project/mcp-salesforce-connector/) on PyPI; runs as a stdio MCP launched per-org by Claude Desktop.
No connected app, no OAuth dance, no copy-pasting session ids — just stay logged into the org in Chrome.
How it fits together
Claude Desktop ── stdio ──▶ this package (Python) ── HTTPS ──▶ Salesforce REST API
│ │
│ └─ reads `sid` cookie ──▶ Chrome cookies on disk
│ on every API call (macOS Keychain)
│
└── one entry in claude_desktop_config.json per Salesforce org
The package is a thin Python shim around `mcp-salesforce-connector`. On every API call, it reads the `sid` cookie that Chrome stores when you're logged into Salesforce, and uses it as the `Authorization` header. That cookie value is identical to a Salesforce session id and is accepted as a Bearer token by the REST API. As long as you keep a Chrome tab open on the org, the session stays alive and Claude inherits the freshness.
Files in this repo
src/salesforce_mcp_auto_auth_chrome/__main__.py— entry point. ReadsSALESFORCE_INSTANCE_URLfrom env, seeds a placeholder access token, installs the
Related Skills
Browser Integration MCP
Control a dedicated Chrome, Edge, or Vivaldi browser profile from Claude Desktop using this secure MCP server
/chrome-cdp — Chrome Browser Automation
Control the user's live Chrome browser via Chrome DevTools Protocol. Connects to real tabs with existing cooki
Relogin
Re-authenticate one Claude Max account (next/next2/next3/next4) through the automated ladder — headless refres
Chrome MCP
Let Claude use the Chrome you're already logged into — real sessions, real cookies, no second browser. MCP ser
View
Open Claude's Corner in the browser (starts local server if needed)
Isolate Dependency Process Boundary
Use a GPL-incompatible-but-needed dependency by running it in a separate process the app talks to over IPC, so
Related Agents
Extension Author
WRITE-access implementer for the browser extension (apps/extension/ — MV3, Chrome + Firefox) and the desktop⇄e
Browser Extension Dev
Expert browser-extension engineer for the operator. Use PROACTIVELY and AUTOMATICALLY for ANY browser-extensio
Plan Polisher
Create or refresh an /aif-plan plan, critique it, and run one refinement round at most. The caller launches an