01
Project inspection
Help an agent understand project structure, configuration, and the current blueprint.
AI-assisted development
Blue Lizard for AI development tools
The intended MCP integration would let compatible AI coding tools interact with structured Blue Lizard capabilities while keeping project context, validation, and diagnostics explicit.
Architecture
A protocol boundary around shared project logic.
This is an intended architecture overview. It does not claim that an MCP server is currently available.
AI Coding AgentCompatible tools and agents
Blue Lizard MCP ServerStructured tool interface
Shared Blue Lizard CoreCommon project capabilities
Project / Build / ValidationIntended execution surface
Intended architecture; implementation details are evolving.
02
Blueprint changes
Support structured creation or modification of backend representations with explicit context.
03
Build and diagnostics
Expose build execution, validation, security diagnostics, and structured error reporting where appropriate.
Security posture
Agent access should be explicit and constrained.
- Least privilege: tools should expose only the permissions needed for a requested operation.
- Explicit approval: destructive or irreversible operations should require clear approval.
- Workspace isolation: project access should remain scoped to the intended workspace.
- Safe secret handling: secrets should not be exposed through prompts, logs, or tool responses.
- Structured responses: tools should return clear, bounded results that agents can interpret reliably.
- Remote authentication: any remote MCP access would require an appropriate authentication model before use.
These are design requirements for a responsible integration, not claims about a currently deployed server.
See where MCP fits in the wider plan.
The roadmap keeps protocol integration connected to the shared core, validation, and developer workflow.
View MCP roadmap items