variables_list — McpStamp Contract Clauses MCP Tool
variables_list
(variables list) is one of 12 tools on the
McpStamp Contract Clauses
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call variables_list from your client
- Claude Code McpStamp Contract Clauses variables_list run in your project directory
- Claude Desktop McpStamp Contract Clauses variables_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Contract Clauses variables_list ~/.cursor/mcp.json
- VS Code McpStamp Contract Clauses variables_list .vscode/mcp.json
- Zed McpStamp Contract Clauses variables_list ~/.config/zed/settings.json
- Windsurf McpStamp Contract Clauses variables_list ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Contract Clauses variables_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Contract Clauses variables_list ~/.gemini/settings.json
- Grok McpStamp Contract Clauses variables_list .mcp.json (in your project root)
- ChatGPT McpStamp Contract Clauses variables_list Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Contract Clauses variables_list Settings → Connectors → Add custom connector
- LangChain McpStamp Contract Clauses variables_list pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http contract-clause-library-proposal-template-docx https://mcp.zovo.one/mcp/clausesOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.