ComplianceAutomator MCP

Name: ComplianceAutomator Public MCP

Version: 0.1.0

Protocol: 2025-03-26

Endpoint: https://www.complianceautomator.com/api/mcp

Mode: public, read-only, stateless

Supported tools

• list_products
  List public ComplianceAutomator products and their framework coverage.
• get_product
  Get a public product by product id.
• list_frameworks
  List supported compliance frameworks and related products.
• get_methodology
  Return a public summary of ComplianceAutomator methodology.
• get_how_it_works
  Return a public summary of how ComplianceAutomator works.
• list_guides
  List public compliance guides from the resource library.
• get_guide
  Get a public compliance guide summary by slug.
• list_blog_posts
  List published blog posts.
• get_blog_post
  Get a public blog post summary by slug.

Request notes

• Use POST https://www.complianceautomator.com/api/mcp for MCP requests.
• Use JSON-RPC request bodies.
• Include an Accept header listing both application/json and text/event-stream.
• Include MCP-Protocol-Version: 2025-03-26 when your client supports it.
• Mcp-Method is recommended; if present, it must match the JSON-RPC method field.
• Mcp-Name is recommended on tools/call; if present, it must match params.name.
• GET /api/mcp is intentionally not used for human docs; it is reserved for MCP transport behavior.
• This endpoint does not expose customer portal, billing, or admin data.

Connection sequence

1. Send initialize as the first request.
2. After a successful initialize response, send notifications/initialized.
3. Use tools/list to discover supported tools.
4. Use tools/call with params.name; if you send Mcp-Name, it must match.

Required headers

Working examples

curl -X POST "https://www.complianceautomator.com/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -H "Mcp-Method: initialize" \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"ExampleClient","version":"1.0.0"}}}'

curl -X POST "https://www.complianceautomator.com/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -H "Mcp-Method: notifications/initialized" \
  --data '{"jsonrpc":"2.0","method":"notifications/initialized"}'

curl -X POST "https://www.complianceautomator.com/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -H "Mcp-Method: tools/list" \
  --data '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

curl -X POST "https://www.complianceautomator.com/api/mcp" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -H "Mcp-Method: tools/call" \
  -H "Mcp-Name: list_products" \
  --data '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"list_products","arguments":{}}}'

Where it fits in the product

ComplianceAutomator is not only a document delivery site anymore. The platform now combines compliance documentation, an audit-readiness workspace, and a public machine-readable surface for AI-native discovery.