MCP Setup Guide
Connect the Polimeo MCP server to your AI agent to scan cookies, draft documents and manage your consent setup.
1. Quick Start
Add the MCP server with the Claude CLI:
$ claude mcp add --transport http polimeo \
https://polimeo.com/api/mcpOr add it to your project's .mcp.json:
{
"mcpServers": {
"polimeo": {
"type": "http",
"url": "https://polimeo.com/api/mcp"
}
}
}The example above uses Claude Code configuration. Other MCP clients that support remote HTTP servers and OAuth may use different configuration keys.
2. Authenticate
The first time your agent calls a tool, the MCP server will initiate an OAuth 2.1 flow. Your browser opens to sign in with email/password or Google, and the agent receives an access token automatically. No API keys to manage.
If you don't have an account yet, sign up at polimeo.com/signup. The OAuth flow will create your session automatically after sign-in.
3. Run the setup prompt
The setup-legal-compliance prompt is the recommended entry point. It walks your agent through the full compliance workflow:
- 1Discovers context from your codebase (or asks for your website URL)
- 2Creates your company with all required details
- 3Registers your website as a service
- 4Scans for cookies with a headless browser
- 5Generates privacy policy, cookie policy, and terms of service
- 6Publishes documents and integrates the consent banner script into your codebase
No parameters are required — just run the prompt and your agent discovers everything from your environment. You can optionally pass websiteUrl and companyName to skip the discovery step.
4. Other prompts
integrate-consent-banner(serviceId)Get the embed code, configuration options, and testing instructions for the consent banner widget.
review-legal-documents(companyId, serviceId)Audit existing documents for completeness, compliance gaps, and cross-reference consistency.
generate-document(companyId, serviceId, documentType)Generate a specific legal document type via the guided questionnaire workflow.
5. Available Tools
Services & Companies
| Tool | Description |
|---|---|
| list_services | List all services accessible to you, grouped by company |
| create_company | Create a new company (guided interactive flow) |
| create_service | Register a website or app under a company |
| get_service_context | Full context for a service: company info, cookies, documents |
Documents
| Tool | Description |
|---|---|
| list_document_types | Available document types and which ones the service already has |
| get_questionnaire | Questions for generating a document, with auto-filled values |
| preview_document | Render a document preview from questionnaire answers |
| generate_document | Generate a draft from answers; cached clients can use the explicit custom_markdown_v1 import envelope documented in premex://guide |
| create_document_draft | Save your own Markdown as an unpublished draft; reuse requestId for identical retries |
| update_document_draft | Edit an unpublished draft using expectedRevision; published and archived text is read-only |
| publish_document | Publish a draft document to the public API |
| list_documents | List all documents for a service |
| get_document | Get full content of a specific document |
Scanner
| Tool | Description |
|---|---|
| scan_cookies | Scan a URL for cookies with a headless browser |
| list_scan_results | Previous scan results for a service |
| import_cookies | Import discovered cookies into the service inventory |
Bug Reports
| Tool | Description |
|---|---|
| create_bug_report | Report an issue with documents, templates, or the platform |
| list_bug_reports | List your bug reports (admins see all) |
| get_bug_report | Get full details of a bug report |
6. Resources
Resources provide read-only context that your agent can attach to conversations without making tool calls.
| URI | Description |
|---|---|
| premex://guide | Platform overview, workflow steps, and capabilities |
| premex://widget-integration | Consent banner embed code, configuration, and programmatic API |
| premex://templates/{type} | Questionnaire reference per document type(privacy_policy, terms_of_service, cookie_policy, eula, disclaimer) |
7. Endpoint
The MCP server is available at a single HTTP endpoint. All MCP clients use this URL for both the streamable-HTTP transport and OAuth discovery.
POST https://polimeo.com/api/mcp