contract — checklist MCP Resource

contract is one of 2 resources on the checklist MCP server. Connect the server and your client can attach it as context.

by client

How to attach contract from your client

• Claude Code checklist Resource/contract run in your project directory
• Claude Desktop checklist Resource/contract ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor checklist Resource/contract ~/.cursor/mcp.json
• VS Code checklist Resource/contract .vscode/mcp.json
• Zed checklist Resource/contract ~/.config/zed/settings.json
• Windsurf checklist Resource/contract ~/.codeium/windsurf/mcp_config.json
• Cline checklist Resource/contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI checklist Resource/contract ~/.gemini/settings.json
• Grok checklist Resource/contract .mcp.json (in your project root)
• ChatGPT checklist Resource/contract Settings → Connectors → Advanced → Developer mode
• Claude.ai checklist Resource/contract Settings → Connectors → Add custom connector
• LangChain checklist Resource/contract pip install langchain-mcp-adapters

Other resources on this server

• pricing

checklist 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 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.