SessionBridge

Share browser sessions with MCP servers — zero API keys

As of June 2026, SessionBridge has 2 users in the Developer Tools category.

Usersno change0%
2
2
Ratingno change0%
— reviews
Reviewsno change0%
Version
1.0.1
Manifest V3

History

3 snapshots

Tracking since Apr 7, 2026.

2.081.50.9199999999999999Apr 7, 2026Jun 7, 2026
View as table
DateUsersRatingReviewsVersion
Apr 7, 20261.0.1
Apr 19, 20261.0.1
Apr 24, 202611.0.1
Now21.0.1

Permissions & access

Permissions
storagenativeMessagingcookies
Host access
https://*.service-now.com/*, https://*.atlassian.net/*, https://*.salesforce.com/*, https://github.com/*

Screenshots

SessionBridge screenshot 1

About

SessionBridge — Zero-Credential Authentication for MCP Servers

SessionBridge eliminates the need for API keys, passwords, and OAuth setup when connecting AI tools to your SaaS platforms. It securely captures your existing browser session and makes it available to local MCP (Model Context Protocol) servers, so they can authenticate using the session you already have.

How it works:
You log into ServiceNow, Jira, Salesforce, or GitHub as you normally would. SessionBridge silently captures your session cookies and CSRF tokens, then writes them to a secure local file. Any compatible MCP server on your machine can read that file to make authenticated API calls — no credentials to configure, rotate, or leak.

Why install SessionBridge?

Zero configuration: No API keys to generate, no OAuth apps to register, no passwords to store. If you can log in with your browser, your MCP server can authenticate.
Works with SSO: Since it uses your existing browser session, it works seamlessly with any SSO provider your organization uses — SAML, OKTA, Azure AD, or any other identity provider.
Multi-platform support: Pre-configured for ServiceNow, Jira, Atlassian, Salesforce, and GitHub. Add any custom domain in seconds via the popup UI.
Secure by design: Session files are stored locally with owner-only permissions (0600). No data is sent to external servers. Sessions expire automatically based on configurable TTL.
Built for MCP: Designed specifically for the Model Context Protocol ecosystem. Pair it with MCP servers like servicenow-mcp to let Claude interact with your enterprise tools using your existing access.
Who is this for?
Developers and IT professionals who use Claude Code, Claude Desktop, or other MCP-compatible AI tools and want to connect them to enterprise platforms without managing separate API credentials.

Getting started:

Install this extension
Install the native messaging host (see documentation)
Log into your SaaS platform in Chrome
Your MCP server authenticates automatically

Technical

Version
1.0.1
Manifest
V3
Size
15.17KiB
Min Chrome
88
Languages
1
Featured
No

Metadata

ID
ifdemmbggfpljiapjfhchcgdkggooaib
Developer ID
u491a1841d9593e9e9c60a85cfead99ec
Developer Email
[email protected]
Created
Apr 7, 2026
Last Updated (Store)
Apr 7, 2026
Last Scraped
Jun 7, 2026
Website
Support URL

Data sourced from the Chrome Web Store · last verified Jun 7, 2026.