clause_export — McpStamp Contract Clauses MCP Tool
clause_export
(clause export) 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 clause_export from your client
- Claude Code McpStamp Contract Clauses clause_export run in your project directory
- Claude Desktop McpStamp Contract Clauses clause_export ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Contract Clauses clause_export ~/.cursor/mcp.json
- VS Code McpStamp Contract Clauses clause_export .vscode/mcp.json
- Zed McpStamp Contract Clauses clause_export ~/.config/zed/settings.json
- Windsurf McpStamp Contract Clauses clause_export ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Contract Clauses clause_export ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Contract Clauses clause_export ~/.gemini/settings.json
- Grok McpStamp Contract Clauses clause_export .mcp.json (in your project root)
- ChatGPT McpStamp Contract Clauses clause_export Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Contract Clauses clause_export Settings → Connectors → Add custom connector
- LangChain McpStamp Contract Clauses clause_export 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.