bindly-claude-code

Bindly for Claude Code adds a knowledge management layer to your Claude Code workflow. It lets you save, search, and organize your thinking into reusable knowledge bindings, with versioned history and project-specific collections (Sets). Once connected, you can use MCP tools to semantic-search your Bindly knowledge, retrieve specific bindings, list bindings within a Set, and create or update bindings and versions. The plugin commands / bindly:save, /bindly:search, and /bindly:organize guide your workflow, enabling you to capture insights as persistent knowledge rather than ephemeral notes. You can also share bindings publicly with a link via a public share mechanism when needed.

Typical usage flows include saving new findings from ongoing work, searching for related bindings to avoid duplication, and organizing related bindings into Sets for project contexts. The MCP tooling supports cross-agent knowledge access, so your Bindly knowledge can be retrieved later from different agents like ChatGPT or other MCP-enabled clients, ensuring continuity across sessions and environments.

Prerequisites:

• A Claude Code account with MCP access and plugin support
• Optional: OAuth setup with Bindly if you want your knowledge to be stored in your Bindly account

Installation steps:

1. Ensure you have Node.js and npm installed on your system.

   • Check: node -v and npm -v

2. Install the MCP server client using npx (as configured in mcp_config):

npx -y bindly-claude-code

3. If required by your environment, set up OAuth credentials for Bindly (these are placeholders in the config and can be omitted if not needed):

export BINDLY_OAUTH_CLIENT_ID="your-client-id"
export BINDLY_OAUTH_CLIENT_SECRET="your-client-secret"

4. Start or connect to the MCP server as instructed by the upstream plugin/package (the command above will pull and run the required server component). If you’re using a managed CLI workflow, follow the plugin installation steps in Claude Code to enable MCP access to Bindly.

5. In Claude Code, install and authenticate the Bindly plugin and then invoke the MCP tools (mcp_search, mcp_get_binding, mcp_list_bindings, etc.) via the MCP interface.

Tips and considerations:

• Bindly stores data in your Bindly account when OAuth is used; otherwise, bindings can be stored locally within the MCP session depending on the plugin configuration.
• Use /bindly:save to capture your current thinking as a binding version. Use /bindly:search to quickly locate related knowledge and avoid duplicating effort.
• Organize related bindings into Sets with /bindly:organize to keep project-specific knowledge grouped and easy to share.
• If you encounter authentication issues, re-run the OAuth flow from Claude Code and re-authenticate the Bindly plugin.
• Ensure your environment variables (if used) do not leak sensitive credentials in logs; prefer secure vaults or secret management where possible.