Control what your AI can see MCP Server Integration
Control what your AI can see. LeanCTX (Lean Context) is the context intelligence layer for AI agents — one local Rust binary that decides what they read, remembers what they learn, guards what they touch, and proves what they save. 60–90% fewer tokens as the receipt. 76 MCP tools, 30+ agents, local-
Technical Integration & Multi-Client Support
The Control what your AI can see MCP Integration translates REST paths, operational endpoints, and tool schemas into standardized Model Context Protocol JSON-RPC 2.0 messages. This allows AI assistants like Claude Desktop, Cursor IDE, VS Code (Cline/Roo Code), and Zed Editor to run tool queries and execute functions seamlessly.
Add stdio configuration block to claude_desktop_config.json.
Configure workspace root at .cursor/mcp.json or Settings -> MCP.
Insert server JSON payload into cline_mcp_settings.json.
Specification & Compatibility Table
| Property | Specification Detail |
|---|---|
| Target Integration | Control what your AI can see (lean-ctx) |
| Directory Category | ai ml |
| Protocol Spec | JSON-RPC 2.0 (stdio) |
| Canonical Path | /mcp-server/lean-ctx/ |
Frequently Asked Questions
How do I access the full JSON configuration for Control what your AI can see?
Click 'Open Full Control what your AI can see MCP Config' above to view the complete parameter schema, environment variable setup, and copy-pasteable JSON configs for Claude Desktop, Cursor, and VS Code.
Does Control what your AI can see require authentication secrets?
Authentication depends on upstream API requirements. Check the environment variable table on the detail page to view required API keys and header tokens.
Browse by Category
Explore MCP server integrations organized by platform and use case.