draft_contract — terms MCP Prompt
draft_contract
is one of 2 prompts on the
terms
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke draft_contract from your client
- Claude Code terms Prompt/draft_contract run in your project directory
- Claude Desktop terms Prompt/draft_contract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor terms Prompt/draft_contract ~/.cursor/mcp.json
- VS Code terms Prompt/draft_contract .vscode/mcp.json
- Zed terms Prompt/draft_contract ~/.config/zed/settings.json
- Windsurf terms Prompt/draft_contract ~/.codeium/windsurf/mcp_config.json
- Cline terms Prompt/draft_contract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI terms Prompt/draft_contract ~/.gemini/settings.json
- Grok terms Prompt/draft_contract .mcp.json (in your project root)
- ChatGPT terms Prompt/draft_contract Settings → Connectors → Advanced → Developer mode
- Claude.ai terms Prompt/draft_contract Settings → Connectors → Add custom connector
- LangChain terms Prompt/draft_contract pip install langchain-mcp-adapters
Other prompts on this server
terms also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, 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 prompt's arguments.