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