ComplianceIQ MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ComplianceIQ MCP Server generate a privacy policy for my e-commerce store"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ComplianceIQ MCP Server
Generate professional compliance documents (privacy policies, terms of service, HIPAA policies, employee handbooks, and more) directly from Claude, Cursor, or any MCP-compatible AI tool.
Setup
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"complianceiq": {
"command": "npx",
"args": ["complianceiq-mcp"],
"env": {
"COMPLIANCEIQ_API_KEY": "your_api_key_here"
}
}
}
}Environment Variables
Variable | Required | Description |
| No (2 free docs/day) | API key from complianceiq.site |
| No | Custom API URL (default: |
Related MCP server: mcp-shiplegal
Tools
generate_document
Generate a compliance document tailored to your industry.
export_document
Export to PDF or DOCX.
list_document_types
List all 12 document types with descriptions.
Links
Website: complianceiq.site
Pricing: complianceiq.site/pricing
Available Tools
3 toolsexport_documentA
Export a compliance document to PDF or DOCX format. Provide the document content (Markdown) from generate_document.
Inputs: format (required), content (required), docType (required), companyName (required).
generate_documentA
Generate a professional compliance document (privacy policy, terms of service, employee handbook, HIPAA policy, etc.) tailored to your industry and company. Returns complete, ready-to-use Markdown.
Inputs: docType (required), industry (required), companyName (required), companyDesc.
list_document_typesA
List all available compliance document types with descriptions, organized by category.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool serves a distinct role: listing document types, generating content, and exporting to file formats. No overlap in functionality, making tool selection unambiguous.
All tool names follow the verb_noun pattern consistently: generate_document, export_document, and list_document_types. This creates a predictable and coherent naming scheme.
With only 3 tools, the set is well-scoped for a focused compliance document generator. Each tool earns its place, covering the essential workflow without unnecessary bloat.
The tool set covers the full lifecycle: discover available document types, generate a document, and export it to a desired format. No obvious gaps exist for the intended purpose.
Maintenance
Related MCP Connectors
Compliant legal documents from your AI assistant: 1,100+ templates, 15 countries, free preview.
One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
AI-powered legal document templates: NDAs, contracts, ToS, privacy policies. Not legal advice.
Run deterministic SaaS contract redlining, GDPR Art. 28 DPA & EU AI Act compliance audits.
Related MCP Servers
- FlicenseBqualityNot gradedmaintenanceEnables the generation of professional, jurisdiction-specific legal documents like privacy policies, terms of service, and cookie policies. It allows users to produce structured HTML legal content by providing specific parties, terms, and service configurations to an AI-driven tool.1-
- AlicenseNot gradedqualityCmaintenanceAnswer a few questions. Get clean, jurisdiction-aware privacy policies and terms of service.MIT
- AlicenseAqualityDmaintenanceProvides AI agents with access to a structured compliance dataset covering privacy and AI regulations across jurisdictions, enabling verifiable answers to regulatory questions via tools and resources.12MIT
- AlicenseAqualityBmaintenanceGenerates legal policies (privacy, terms, cookies, etc.) directly from AI coding tools by analyzing codebase context.16120 npmMIT