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