> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/cipp/settings/features.md).

# Features

Feature flags control the visibility of parts of CIPP that are either still in preview or on their way out. Disabling a flag hides the relevant pages, disables the API endpoints behind them, and stops any scheduled timers the feature uses, so it is a genuine switch rather than a cosmetic one.

To change a flag, open the actions menu on its row and choose **Enable Feature** or **Disable Feature**. Multiple flags can be changed at once by selecting their checkboxes and using the bulk actions dropdown.

### Current Feature Flags

| Feature                | Status      | Description                                                                                                                                                      |
| ---------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Best Practice Analyser | Deprecation | This feature is being deprecated in favour of the new reporting database cache being used by Dashboard v2 and will be removed in a future release.               |
| MCP Server             | Beta        | Model Context Protocol (MCP) server endpoint that exposes CIPP's read-only API surface as tools for AI clients. Disabled by default; enable to allow MCP access. |

{% hint style="info" %}
CIPP maintains further internal flags that are not shown on this page. Those govern behaviour determined by how your instance is hosted rather than by preference, so they are set automatically and cannot be toggled.
{% endhint %}

## Table Details

| Column      | Description                                         |
| ----------- | --------------------------------------------------- |
| Name        | The name of the feature the flag controls.          |
| Enabled     | Whether the feature is currently switched on.       |
| Description | What the feature does, and why it is behind a flag. |

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Enable Feature</td><td>Switches the feature on, restoring its pages, endpoints and any scheduled timers it uses. Only offered for features that are currently disabled.</td><td>true</td></tr><tr><td>Disable Feature</td><td>Switches the feature off, hiding its pages and disabling its endpoints and timers. Only offered for features that are currently enabled.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

{% hint style="info" %}
The Extended Info flyout lists exactly what a flag governs, namely the pages it shows, the API endpoints it enables, and any scheduled timers it controls. Check it before disabling a feature, so you know what stops working.
{% endhint %}

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cipp.app/user-documentation/cipp/settings/features.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.