contract — scope change MCP Resource

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

by client

How to attach contract from your client

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

Other resources on this server

• pricing

scope change 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.