Sahadeva interactive reading view — Sahadeva MCP Resource
Sahadeva interactive reading view
is one of 10 resources on the
Sahadeva
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Sahadeva interactive reading view from your client
- Claude Code Sahadeva Resource/Sahadeva interactive reading view run in your project directory
- Claude Desktop Sahadeva Resource/Sahadeva interactive reading view ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sahadeva Resource/Sahadeva interactive reading view ~/.cursor/mcp.json
- VS Code Sahadeva Resource/Sahadeva interactive reading view .vscode/mcp.json
- Zed Sahadeva Resource/Sahadeva interactive reading view ~/.config/zed/settings.json
- Windsurf Sahadeva Resource/Sahadeva interactive reading view ~/.codeium/windsurf/mcp_config.json
- Cline Sahadeva Resource/Sahadeva interactive reading view ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sahadeva Resource/Sahadeva interactive reading view ~/.gemini/settings.json
- Grok Sahadeva Resource/Sahadeva interactive reading view .mcp.json (in your project root)
- ChatGPT Sahadeva Resource/Sahadeva interactive reading view Settings → Connectors → Advanced → Developer mode
- Claude.ai Sahadeva Resource/Sahadeva interactive reading view Settings → Connectors → Add custom connector
- LangChain Sahadeva Resource/Sahadeva interactive reading view pip install langchain-mcp-adapters
Other resources on this server
- Sahadeva methodology and safety contract
- Recommended MCP workflows
- Rule citation and publication policy
- Blind validation protocol for life-theme ranking
- Specialist tools for explicit advanced workflows
- Lal Kitab coverage and controlled-disclosure policy
- Lal Kitab remedy-engine coverage and execution policy
- Complete evidence-first prediction method and tool routing contract
- MCP privacy, anti-exfiltration and untrusted-data contract
Sahadeva also offers 8 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.