Workers Bridge MCP
This guide connects the stdio MCP server to Codex CLI and fetches authenticated YouTube, X, and Reddit data through direct destination connections. Worker relay configuration is covered in docs/manual.md.
Before you start
- macOS for the bundled Chrome cookie exporter (manual DevTools export works on any platform).
- Python 3.12+ and uv.
- Codex CLI.
- Chrome signed in to the services you want to read, in the profile you will export from.
1. Extract cookies from Chrome
Cookies are full account credentials. Keep the values private, never commit them, and never paste them into chat.
Option A: bundled exporter (macOS)
Extract each service directly into its environment variable with uvx. This
requires mcp-workers-bridge 0.6.0 or newer:
export YOUTUBE_STORAGE_STATE_JSON="$(
uvx --system-certs --from 'mcp-workers-bridge[cookies]' \
chrome-storage-state youtube --profile "Default" --stdout
)"
export X_STORAGE_STATE_JSON="$(
uvx --system-certs --from 'mcp-workers-bridge[cookies]' \
chrome-storage-state x --profile "Default" --stdout
)"
export REDDIT_STORAGE_STATE_JSON="$(
uvx --system-certs --from 'mcp-workers-bridge[cookies]' \
chrome-storage-state reddit --profile "Default" --stdout
)"
Use the published PyPI package
Run the server without cloning:
uvx mcp-workers-bridge
Or install it persistently:
uv tool install mcp-workers-bridge
# or
pipx install mcp-workers-bridge
The package page is pypi.org/project/mcp-workers-bridge. To download the wheel and source archive without installing, use Download files on that page, or:
python -m pip download mcp-workers-bridge --no-deps -d dist
Versions before 0.6.0 do not include the chrome-storage-state exporter. For
a repository checkout, run uv sync --system-certs --extra cookies and replace
each uvx ... chrome-storage-state command above with
.venv/bin/chrome-storage-state.
Default is Chrome's first profile. The directory name depends on the person
and browser setup; list ~/Library/Application Support/Google/Chrome/ and pass
the profile that is signed in (for example --profile "Profile 1").
The exporter reads the "Chrome Safe Storage" key from Keychain (macOS may ask
for permission once), copies the cookie database to a temporary directory,
decrypts matching cookies, and prints storage-state JSON with --stdout. Use
--output PATH instead if you prefer a private mode-600 file. --chrome-root
can point at a non-default Chrome installation.
Option B: Chrome DevTools (any platform)
- Open Chrome, then View > Developer > Developer Tools.
- Open the Application tab, then Storage > Cookies.
- Select
https://www.youtube.com,https://x.com, orhttps://old.reddit.com. - Copy the required names and values into a JSON object for the environment variable in step 2:
{
"cookies": [
{
"name": "SAPISID",
"value": "<value>",
"domain": ".youtube.com",
"path": "/",
"expires": -1,
"secure": true
}
],
"origins": []
}
Required cookies per service:
| Service | Required cookie(s) | Export all cookies for |
|---|---|---|
| YouTube history | SAPISID or __Secure-3PAPISID |
youtube.com |
| X | auth_token and ct0 |
x.com |
reddit_session |
reddit.com |
YouTube captions for public videos do not need a session.
2. Set the environment variables
Direct mode needs only the storage-state variable for each service you use:
| Data | Minimum variable |
|---|---|
| YouTube history | YOUTUBE_STORAGE_STATE_JSON |
| X | X_STORAGE_STATE_JSON |
REDDIT_STORAGE_STATE_JSON |
|
| YouTube captions only | none |
If you used the exporter in step 1, the variables are already set for that shell; rerun those export commands in a new shell. If you used DevTools, assign the JSON objects directly:
export YOUTUBE_STORAGE_STATE_JSON='{"cookies":[...],"origins":[]}'
export X_STORAGE_STATE_JSON='{"cookies":[...],"origins":[]}'
export REDDIT_STORAGE_STATE_JSON='{"cookies":[...],"origins":[]}'
3. Register with Codex CLI
Option A: use the project config
Trust this checkout in ~/.codex/config.toml:
[projects."/path/to/mcp-workers-bridge"]
trust_level = "trusted"
Then run codex from anywhere inside the checkout. The project-scoped
.codex/config.toml defines the MCP server entry and forwards the variables
listed above.
Option B: register a user-level server
Recommended PyPI registration:
codex mcp add workers-bridge -- uvx mcp-workers-bridge
Codex stores uvx as the command with mcp-workers-bridge as its argument and
runs the published package on demand.
For a repository install instead:
cd /path/to/mcp-workers-bridge
codex mcp add workers-bridge -- "$(pwd)/.venv/bin/mcp-workers-bridge"
Add the environment pass-through list to the entry in ~/.codex/config.toml:
[mcp_servers.workers-bridge]
command = "uvx"
args = ["mcp-workers-bridge"]
env_vars = [
"YOUTUBE_STORAGE_STATE_JSON",
"YOUTUBE_TIMEZONE",
"YOUTUBE_CACHE_DIR",
"X_STORAGE_STATE_JSON",
"REDDIT_STORAGE_STATE_JSON",
"UV_SYSTEM_CERTS"
]
For a repository install, use the repository .venv path as command.
Restart Codex after changing the config, then verify:
codex mcp list
codex mcp get workers-bridge
4. Verify the connection
In a Codex CLI session, run /mcp and confirm the server is connected. Then:
- Call
bridge_configurationand confirmmodeisdirect. - Call
workers_youtube_captionswith"dQw4w9WgXcQ"(no session needed). - Call
workers_youtube_historywithrefresh=falsebefore the first refresh, then withrefresh=true. - Call
workers_x_homeandworkers_reddit_identity.
Missing sessions produce a per-tool configuration error; they do not prevent the server from starting.
Documentation
- PyPI package: published
server package used by
uvx mcp-workers-bridge. - docs/manual.md: full configuration, tool reference, cache, acceptance results, and security boundaries.
- docs/codex-cloud.md: Codex Cloud setup, secrets, OIDC, and S3 permissions.
- infra/service-bridge-workers/README.md: Worker deployment, Terraform, Access, and acceptance runbook.
- infra/service-bridge-workers/API.md: HTTPS contract.
Metadata
Release files for mcp-workers-bridge 0.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mcp_workers_bridge-0.6.0.tar.gz | 52.2 kB | With provenance | Details for mcp_workers_bridge-0.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mcp_workers_bridge-0.6.0-py3-none-any.whl | Python 3 | none | any | Details for mcp_workers_bridge-0.6.0-py3-none-any.whl |
Total release size: 94.9 kB
Release files / mcp_workers_bridge-0.6.0.tar.gz
| Download URL | mcp_workers_bridge-0.6.0.tar.gz |
|---|---|
| Size | 52.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3764c1c08c194cdf544eaddf5da5734fe81654c467284d4bf3810966c6709f14
|
|
BLAKE2b-256 checksum How to use checksums |
3063d923ca998c732f35b631252ca168857a72a89962439c63e63c119ad99363
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logRelease files / mcp_workers_bridge-0.6.0-py3-none-any.whl
| Download URL | mcp_workers_bridge-0.6.0-py3-none-any.whl |
|---|---|
| Size | 42.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01f38da418a74ca2e5dd3080ba26f481489362d22cf294dc72181bd3f29d247b
|
|
BLAKE2b-256 checksum How to use checksums |
0274d34e749d70040415321a5541f1b3b7f520631b481e79acba18ee199711c4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logSecurity for mcp-workers-bridge 0.6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for mcp_workers_bridge-0.6.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.