01 - Get Started with a MCP Setup
Give AI Agents the governed access they need
03 - FAQ's
Frequently asked questions
Get started with Blekline
What is an MCP ingress control plane?
Blekline sits between your AI agents and everything they touch: model APIs, tools, and sandboxes. Every call is masked, policy-checked, and audited before it executes.
Do I need an account to start?
No. Local secret scanning and tool enforcement work offline via @blekline/contracts. You need a workspace token only for cloud PII masking, fleet policy, and audit events.
How is Blekline different from prompt guardrails?
Prompt instructions are best-effort. Blekline enforces policy at the MCP call boundary, before the model or tool runs, regardless of which model or client you use.
CApabilities & Solutions
Does Blekline work with Cursor and Claude?
Yes. Blekline connects over MCP to Cursor, Claude Desktop, and Codex. One server covers all models; no changes to your agent code.
What’s the difference between mcp-server and mcp-proxy?
Server gives agents mask/enforce tools. Proxy sits in front of downstream MCP (e.g. Daytona) and blocks tool calls before they execute.
Are prompts stored in Blekline?
No. Default audit events are metadata only: action taken, entity counts, tool name, client surface. No raw prompt bodies or full tool arguments.
