> 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/integrations/sdk-and-libraries/mcp-servers/distribution-mcp-server.md).

# Distribution MCP Server

The **DecisionRules MCP Distribution Server** gives MCP-compatible clients access to managed DecisionRules content. It is designed for templates, reusable functions, and curated resource links.

Use this server when you want shared DecisionRules assets available directly in your AI tools or automation workflows.

### MCP Distribution Server Endpoint

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

{% hint style="warning" %}
The URL above is an MCP endpoint and cannot be opened in a browser.\
It is only for MCP-compatible clients.
{% endhint %}

### Prerequisites

Before you begin, ensure that you have:

* An **MCP-compatible client** (e.g., IDE plugin, AI assistant, or other tools supporting MCP).
* Network access to the hosted MCP Distribution Server.

Your infrastructure must allow outbound access to the Distribution Server. If needed, review [Network prerequisites](/doc/other-deployment-options/docker-and-on-premise/prerequisites.md).

### Configuration

To connect your client, configure it with the hosted endpoint:

```json
{
  "mcpServers": {
    "decisionrulesDistribution": {
      "url": "https://distribution.decisionrules.io/mcp"
    }
  }
}
```

**Explanation:**

* `"decisionrulesDistribution"` – a descriptive name for the server connection.
* `"url"` – the hosted MCP Distribution Server endpoint.

Once configured, your client can access managed DecisionRules content directly.

### What the server provides

Through this server, MCP clients can work with:

* **Predefined templates** for faster rule creation
* **Reusable functions and components**
* **Links to documentation and Academy resources**
* **Structured content** for AI assistants and automation flows

This keeps shared assets centralized and consistent across environments.

### Common use cases

After setup, your client can use the server to:

* discover available templates
* retrieve reusable functions
* surface learning resources inside AI workflows
* keep managed content separate from runtime or documentation MCP servers

### Benefits

* **Centralized content delivery**: one place for managed DecisionRules assets.
* **Consistent usage**: shared templates and functions stay aligned.
* **Seamless integration**: works with MCP-compatible clients without local setup.
* **Clear separation**: keeps distribution content separate from documentation and runtime services.

### Next Steps

1. Add the Distribution Server endpoint to your MCP client.
2. Verify the client can reach `https://distribution.decisionrules.io/mcp`.
3. Start using shared templates, functions, and managed resources in your workflows.

✅ Your MCP client is now ready to use DecisionRules managed content.


---

# 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.decisionrules.io/doc/integrations/sdk-and-libraries/mcp-servers/distribution-mcp-server.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.