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