ComplianceIQ MCP Server
ComplianceIQ MCP 服务器
直接从 Claude、Cursor 或任何兼容 MCP 的 AI 工具生成专业的合规文档(隐私政策、服务条款、HIPAA 政策、员工手册等)。
设置
Claude Desktop
添加到你的 claude_desktop_config.json:
{
"mcpServers": {
"complianceiq": {
"command": "npx",
"args": ["complianceiq-mcp"],
"env": {
"COMPLIANCEIQ_API_KEY": "your_api_key_here"
}
}
}
}环境变量
变量 | 必需 | 描述 |
| 否(每天免费 2 份文档) | 来自 complianceiq.site 的 API 密钥 |
| 否 | 自定义 API URL(默认: |
Related MCP server: mcp-shiplegal
工具
generate_document
生成针对你所在行业定制的合规文档。
export_document
导出为 PDF 或 DOCX 格式。
list_document_types
列出所有 12 种文档类型及其描述。
链接
Available Tools
3 toolsexport_documentA
Export a compliance document to PDF or DOCX format. Provide the document content (Markdown) from generate_document.
| Name | Required | Description | Default |
|---|---|---|---|
| format | Yes | Export format: pdf or docx. | |
| content | Yes | Document content in Markdown (from generate_document output). | |
| docType | Yes | Document type identifier (e.g. privacy, terms, handbook). | |
| companyName | Yes | Company name for the document header. |
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.
| Name | Required | Description | Default |
|---|---|---|---|
| docType | Yes | Document type: privacy, terms, handbook, data-handling, aup, security, cookie, incident, hipaa, osha, whistleblower, remote-work | |
| industry | Yes | Your industry for regulatory tailoring. | |
| companyDesc | No | Brief company description for more specific language. | |
| companyName | Yes | Your company or organization name. |
list_document_typesA
List all available compliance document types with descriptions, organized by category.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
3 tool updates
v0.1.0- First observed
export_document - First observed
generate_document - First observed
list_document_types
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.
41Run 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