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