license_activate — contract clause library proposal template docx MCP Tool
license_activate
(license activate) is one of 12 tools on the
contract clause library proposal template docx
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call license_activate from your client
- Claude Code contract clause library proposal template docx license_activate run in your project directory
- Claude Desktop contract clause library proposal template docx license_activate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor contract clause library proposal template docx license_activate ~/.cursor/mcp.json
- VS Code contract clause library proposal template docx license_activate .vscode/mcp.json
- Zed contract clause library proposal template docx license_activate ~/.config/zed/settings.json
- Windsurf contract clause library proposal template docx license_activate ~/.codeium/windsurf/mcp_config.json
- Cline contract clause library proposal template docx license_activate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI contract clause library proposal template docx license_activate ~/.gemini/settings.json
- Grok contract clause library proposal template docx license_activate .mcp.json (in your project root)
- ChatGPT contract clause library proposal template docx license_activate Settings → Connectors → Advanced → Developer mode
- Claude.ai contract clause library proposal template docx license_activate Settings → Connectors → Add custom connector
- LangChain contract clause library proposal template docx license_activate 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 24 September 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.