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