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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- bindry-connect
- description
- 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.
03 SKILL.md 正文
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.
- Explain up front: this needs an API key — the same one already used for pinned
bindry-syncworks 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 aBINDRY_API_TOKENenvironment variable rather than pasting it directly. - Need
--api-base <url>(the Bindry API's base URL — ask if not obvious from context, e.g. from an existingbindry.config.jsonin a project this user has already synced). - 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 - After running it, confirm the server shows as connected (list configured MCP servers and check
bindry's status). If it reports a connection failure, report exactly what it said (bad API base, network issue, or an invalid/expired key show up as different failures — don't guess which without checking). - Once connected, tell the user live-mode skills are ready to use — syncing a Binder with
--mode livewill now compile skills the agent can actually call MCP tools through, and thebindry-checkskill will report them as "live (always current)" rather than stale or unknown.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.