bind-mcp
Bind Protocol MCP server for credential verification, policy authoring, and zero-knowledge proof generation.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/jason-c-child/bind-protocol-mcpBind MCP Server — Agent Skill Guide
You have access to the Bind Protocol MCP server. This document teaches you how to use it.
Prerequisites & Installation
Requirements
- Node.js >= 18 — Required to run the server (
npxhandles package installation automatically) - Bind account — Required for API-backed tools. Create one at https://dashboard.bindprotocol.xyz
- Agent key (
idbr_agent_...) — Required for API-backed tools. Regular API keys (idbr_) are not supported for MCP.
Credential Setup
Bind uses agent keys for MCP authentication. Agent keys are scoped API keys that let org admins control exactly which tools are available, set daily rate limits, and get audit logs.
| Key type | Format | MCP supported |
|---|---|---|
| Agent key | idbr_agent_<keyId>_<secret> | Yes — required for API-backed tools |
| Regular API key | idbr_<keyId>_<secret> | No — rejected by MCP server |
To create an agent key:
- Sign in at https://dashboard.bindprotocol.xyz
- Navigate to Settings > Agent Keys
- Select which tool categories the key can access (e.g., credential verification only, or policy authoring + verification)
- Copy the key — it is shown only once
MCP Server Configuration
Add the server to your MCP client configuration. The exact file depends on your tool:
| Tool | Config file |
|---|---|
| Claude Code | .mcp.json in your project root, or ~/.claude/claude_desktop_config.json |
| Claude Desktop | Settings > Developer > Edit Config |
| Cursor | .cursor/mcp.json in your project root |
| Windsurf | MCP settings |
Configuration JSON:
{
"mcpServers": {
"bind": {
"command": "npx",
"args": ["@bind-protocol/mcp-server"],
"env": {
"BIND_API_KEY": "${BIND_API_KEY}"
}
}
}
}
The BIND_API_KEY environment variable must be set in your shell to your agent key before launching your AI tool. Never hardcode the key directly in config files — always use environment variable references to avoid accidental credential leakage in shared configs or repositories.
Environment variables:
| Variable | Required | Default | Description |
|---|---|---|---|
BIND_API_KEY | For API-backed tools | — | Agent key (idbr_agent_...). Without this, only local tools are available. |
BIND_API_URL | No | https://api.bindprotocol.xyz | Base URL for API calls |
BIND_RECEIPTS_PATH | No | ~/.bind/receipts | Directory for receipt chain data |
LOG_LEVEL | No | info | Logging verbosity (debug, info, warn, error) |
Verifying the Setup
If you do not have bind tools available, prompt the user to complete the setup above. You can test connectivity by calling bind_whoami — if it returns org info, the agent key is authenticated. Without a BIND_API_KEY, only local tools (parse, verify, hash) are available.
Architecture & Data Flow
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-jason-c-child-bind-protocol-mcp": {
"enabled": true,
"auto_update": true
}
}
}