MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
Stdio MCP server exposing Blekline governance tools for all verified client surfaces. Runs locally from the @blekline/mcp-server npm package. Needs 3 environment variables to run.
MCP server Claude CodeCodexCursor +2
One of 2 in .mcp.json
MCP proxy router that intercepts downstream tool calls, runs Blekline enforcement (mask/block), then forwards approved calls to a downstream MCP server (Daytona, Modal, E2B, Cloudflare, Vercel Sandbox, or mock). Runs locally from the @blekline/mcp-proxy npm package. Needs 4 environment variables to run.
Command Claude Code
Initialize Blekline Codex hooks in this workspace.
Command Claude Code
Mask the current user text with bleklinemaskprompt before further tool use.
Command Claude Code
Check Codex hooks.json uses shell wrappers and tokens are placeholders.
Hook Claude Code
One of 4 in hooks.json
Runs when a session starts on startup and resume, executing blekline-session-start.sh. From Blekline/blekline-oss.
Hook Claude Code
One of 4 in hooks.json
Runs when you submit a prompt, before the agent sees it, executing blekline-user-prompt-submit.sh. From Blekline/blekline-oss.
Hook Claude Code
One of 4 in hooks.json
Runs before the agent uses a tool, executing blekline-pre-tool-use.sh. From Blekline/blekline-oss.
Hook Claude Code
One of 4 in hooks.json
Runs after a tool call finishes, executing blekline-post-tool-use.sh. From Blekline/blekline-oss.
Skill Claude CodeCodex
After a Codex hook block, do not reconstruct secrets. Silent auto-send is ingress Responses.
Skill Claude CodeCodex
Install Blekline Codex hook wrappers (.sh and .cmd) via @blekline/codex-hooks init.
Skill Claude CodeCodex
Mask user text with PII or secrets before Codex tools or the model see it.
Skill Claude CodeCodex
Route downstream MCP tools through blekline-proxy for argument policy checks.
Cursor rule Cursor
Blekline chat guard — mask prompts via MCP and respect Cursor hook blocks.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: