Preloop

| Variable | Default | Description |
|----------|---------|-------------|
| REGISTRATION_ENABLED | true | Enable self-registration. Set to false to disable public signups and require admin invitation. |

Preloop Enterprise Edition extends the open-source core with additional features for teams and organizations:

| Feature | Open Source | Enterprise |
|---------|:-----------:|:----------:|
| MCP Server with 6 built-in tools | ✅ | ✅ |
| Basic approval workflows | ✅ | ✅ |
| Email notifications | ✅ | ✅ |
| Mobile app notifications (iOS/Watch; Android) | ✅ | ✅ |
| Issue tracker integration | ✅ | ✅ |
| Vector search & duplicate detection | ✅ | ✅ |
| Agentic flows | ✅ | ✅ |
| Web UI | ✅ | ✅ |
| Role-Based Access Control (RBAC) | ❌ | ✅ |
| Team management | ❌ | ✅ |
| CEL conditional approval policies | ❌ | ✅ |
| Team-based approvals with quorum | ❌ | ✅ |
| Approval escalation | ❌ | ✅ |
| Slack notifications | ❌ | ✅ |
| Mattermost notifications | ❌ | ✅ |
| Admin dashboard | ❌ | ✅ |
| Audit logging & impersonation tracking | ❌ | ✅ |
| Billing & subscription management | ❌ | ✅ |
| Priority support | ❌ | ✅ |

Contact [email protected] for Enterprise Edition licensing.

- GET /api/v1/tool-configurations - List tool configurations
- POST /api/v1/tool-configurations - Create tool configuration
- PUT /api/v1/tool-configurations/{id} - Update tool configuration
- DELETE /api/v1/tool-configurations/{id} - Delete tool configuration

The Preloop API now includes integrated MCP tool endpoints with dynamic tool filtering, allowing any HTTP-based MCP client to connect directly. This is the recommended way to automate issue management workflows.

Authentication: All MCP endpoints use the same Bearer Token authentication as the rest of the API.

Dynamic Tool Visibility: MCP tools are only visible when your account has one or more trackers configured. This ensures tools have the necessary context to operate effectively. If you connect with an account that has no trackers, you will see an empty tool list.

Connecting with Claude Code:

You can connect Claude Code directly to your Preloop instance using the claude mcp add command.

1. Get your Preloop API Key: You can find or create an API key in your Preloop user settings.
2. Add the MCP Server: Run the following command, replacing YOUR_PRELOOP_URL and YOUR_API_KEY with your details.

    claude mcp add \
      --transport http \
      --header "Authorization: Bearer YOUR_API_KEY" \
      preloop \
      https://YOUR_PRELOOP_URL/mcp/v1
    

- --transport http: Specifies that the server uses the HTTP transport.
- --header "Authorization: Bearer YOUR_API_KEY": Provides the necessary authentication header for all requests.
- preloop: This is the name you will use to refer to the server (e.g., @preloop get_issue ...).
- https://YOUR_PRELOOP_URL/mcp/v1: This is the base URL for the Preloop MCP endpoints.

Example Workflow (using curl):

If you are not using an MCP client and want to interact with the tool endpoints directly, you can use any HTTP client like curl.

1. Create an Issue:

    curl -X POST "https://YOUR_PRELOOP_URL/api/v1/mcp/create_issue" \

    -H "Authorization: Bearer YOUR_API_KEY" \

    -H "Content-Type: application/json" \

    -d '{

      "project": "your-org/your-project",

      "title": "New Feature Request",

      "description": "Add a dark mode to the dashboard."

    }'

    

Preloop provides approval workflows for tool execution. Control which operations require approval before execution.

Key Concepts:
- Tool Configuration: Enable/disable tools and assign approval policies
- Approval Policies: Define approval requirements, approvers, timeouts, and notification channels
- Email Notifications: Receive approval requests via email with one-click approve/decline

Example: Create an Approval Policy

curl -X POST "https://YOUR_PRELOOP_URL/api/v1/approval-policies" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "name": "Critical Operations",
  "description": "Require approval for critical issue operations",
  "is_default": false,
  "approver_user_ids": ["user-id-1", "user-id-2"],
  "approvals_required": 1,
  "timeout_seconds": 600,
  "notification_channels": ["email"]
}'

Configure a tool to require approval:

curl -X POST "https://YOUR_PRELOOP_URL/api/v1/tool-configurations" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "tool_name": "update_issue",
  "tool_source": "preloop_builtin",
  "is_enabled": true,
  "approval_policy_id": "<policy_id_from_above>"
}'

> Enterprise Features: Preloop Enterprise Edition adds CEL-based conditional approvals, team-based approvals with quorum, escalation policies, and multi-channel notifications (Slack, Mattermost, mobile push). Contact [email protected] for more information.