Unslop canon index (entry point) — Unslop MCP Resource
Unslop canon index (entry point)
is one of 1 resource on the
Unslop
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Unslop canon index (entry point) from your client
- Claude Code Unslop Resource/Unslop canon index (entry point) run in your project directory
- Claude Desktop Unslop Resource/Unslop canon index (entry point) ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Unslop Resource/Unslop canon index (entry point) ~/.cursor/mcp.json
- VS Code Unslop Resource/Unslop canon index (entry point) .vscode/mcp.json
- Zed Unslop Resource/Unslop canon index (entry point) ~/.config/zed/settings.json
- Windsurf Unslop Resource/Unslop canon index (entry point) ~/.codeium/windsurf/mcp_config.json
- Cline Unslop Resource/Unslop canon index (entry point) ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Unslop Resource/Unslop canon index (entry point) ~/.gemini/settings.json
- Grok Unslop Resource/Unslop canon index (entry point) .mcp.json (in your project root)
- ChatGPT Unslop Resource/Unslop canon index (entry point) Settings → Connectors → Advanced → Developer mode
- Claude.ai Unslop Resource/Unslop canon index (entry point) Settings → Connectors → Add custom connector
- LangChain Unslop Resource/Unslop canon index (entry point) pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 12 October 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.