Rendering contract — Magist MCP Resource
Rendering contract
is one of 3 resources on the
Magist
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Rendering contract from your client
- Claude Code Magist Resource/Rendering contract run in your project directory
- Claude Desktop Magist Resource/Rendering contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Magist Resource/Rendering contract ~/.cursor/mcp.json
- VS Code Magist Resource/Rendering contract .vscode/mcp.json
- Zed Magist Resource/Rendering contract ~/.config/zed/settings.json
- Windsurf Magist Resource/Rendering contract ~/.codeium/windsurf/mcp_config.json
- Cline Magist Resource/Rendering contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Magist Resource/Rendering contract ~/.gemini/settings.json
- Grok Magist Resource/Rendering contract .mcp.json (in your project root)
- ChatGPT Magist Resource/Rendering contract Settings → Connectors → Advanced → Developer mode
- Claude.ai Magist Resource/Rendering contract Settings → Connectors → Add custom connector
- LangChain Magist Resource/Rendering contract pip install langchain-mcp-adapters
Other resources on this server
Magist also offers 3 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 16 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.