> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/decisionrules-applications/decisionrules-distribution-server.md).

# DecisionRules Distribution Server

### Overview

The **DecisionRules Distribution Server** is a centralized service that provides **managed content and resources** for DecisionRules environments.

It serves as a single source of truth for reusable assets such as templates, functions, and learning materials, ensuring consistency across all users and deployments.

### Purpose

The Distribution Server is responsible for:

* Providing **predefined templates** for faster rule creation
* Distributing **reusable functions and components**
* Delivering **links to Documentation and  Academy**
* Centralizing access to managed content across environments

### MCP Server Integration

The Distribution Server exposes its content via an **MCP (Model Context Protocol) server**, allowing AI assistants and agents to access and use this content dynamically.

#### MCP Endpoint

* `https://distribution.decisionrules.io/mcp`

Through this endpoint, clients can:

* Discover available templates, functions, and resources  
* Retrieve structured content for AI workflows  
* Integrate DecisionRules knowledge into assistants and automation  

### Setup

To successfully run DecisionRules with a Distribution server, your infrastructure must allow outbound access to it

{% content-ref url="/pages/le7CRo6cx4c6OKBmnWNG" %}
[Prerequisites](/doc/other-deployment-options/docker-and-on-premise/prerequisites.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.decisionrules.io/doc/decisionrules-applications/decisionrules-distribution-server.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.