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