Menu

Individual skill

bindry-connect

One-time setup connecting Codex to the Bindry MCP server, for live-mode skills. Use when the user wants to enable live mode for Bindry skills or asks to connect Codex to Bindry's MCP server.

plugins/bindryai/Plugins/skills/bindry-connect/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Connect this machine to the Bindry MCP server so `--mode live` skills (compiled by the `bindry-sync` skill)
actually work. This is a one-time, per-machine/user step — it isn't tied to any particular project or Binder,
and only needs to happen once even if the user syncs several Binders live later.

1. Explain up front: this needs an API key — the same one already used for pinned `bindry-sync` works here
   too, no separate scope or permission to grant. Generate one from the workspace's team page in Bindry (not
   Account settings — a key is scoped to whichever workspace's team page made it). Recommend the user put it
   in a `BINDRY_API_TOKEN` environment variable rather than pasting it directly.
2. Need `--api-base <url>` (the Bindry API's base URL — ask if not obvious from context, e.g. from an existing
   `bindry.config.json` in a project this user has already synced).
3. This changes standing local CLI configuration (adds an MCP server to this machine's Codex config) — state
   the exact command below and get explicit confirmation before running it, don't run it silently:
   ```
   codex mcp add bindry --url <api-base>/api/mcp --bearer-token-env-var BINDRY_API_TOKEN