# Server installation

## Compatibility

The Wedolow MCP Server is compatible with:

* Windows 10/11
* Ubuntu 20.04+
* Debian 11+
* Fedora 32+
* OpenSUSE 15.3+

## Prerequisites

{% tabs %}
{% tab title="Linux" %}
Install [Python 3.10 or higher](https://www.python.org/downloads/).
{% endtab %}

{% tab title="Windows" %}
Install [Python 3.10 or higher](https://www.python.org/downloads/).

Install [Visual Studio C++ Redistributable 2017](https://aka.ms/vs/17/release/vc_redist.x64.exe). Double-click on the downloaded file and follow the steps to install it.

Run the following command:

```powershell
Get-ExecutionPolicy
```

If result is `Restricted`, then you must [change the execution policy](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.4) to `RemoteSigned` or `Unrestricted` (less safe). For this, open a Powershell terminal **as an administrator**.

You may do that by setting execution policy to your current user:

```powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
```

You may also apply it to the whole local machine:

```powershell
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine
```

After running one of these commands, `Get-ExecutionPolicy` should return `RemoteSigned`.
{% endtab %}
{% endtabs %}

## Installation methods

### Using VSCode Extension

In VSCode, install [WedoLow extension](https://marketplace.visualstudio.com/items?itemName=WedoLow.wedolow) from the store.

<figure><img src="/files/DAThXPykOOvDa7SqnXWx" alt=""><figcaption><p>Install WedoLow extension</p></figcaption></figure>

Then, follow the instructions on the welcome page that shows up.

<figure><img src="/files/siaYi7iBmzhaKzk0BGs1" alt=""><figcaption><p>WedoLow extension welcome page</p></figcaption></figure>

### Manually

First, we advise you to use a Python virtual environment (generally recommended). In this guide, we will use a virtual environment `.venv-wedolow` created in the user workspace. To create the virtual environment and load it, and run:

{% tabs %}
{% tab title="Linux (Bash)" %}

```bash
python -m venv ~/.venv-wedolow
source ~/.venv-wedolow/bin/activate
```

{% endtab %}

{% tab title="Windows (PowerShell)" %}

```powershell
python -m venv "${env:USERPROFILE}\.venv-wedolow"
. "${env:USERPROFILE}\.venv-wedolow\Scripts\Activate.ps1"
```

{% endtab %}
{% endtabs %}

{% hint style="info" %}
Depending on your Python installation, you may need to explicitly use `python3` instead of `python` command.
{% endhint %}

**In the same terminal**, install the WHL package (adapt the dame of the package):

{% tabs %}
{% tab title="Linux" %}

```bash
pip install --index-url https://__token__:<your_token>@gitlab.com/api/v4/projects/75458460/packages/pypi/simple/ wedolow-mcp-server-linux
```

{% endtab %}

{% tab title="Windows" %}

```
pip install --index-url https://__token__:<your_token>@gitlab.com/api/v4/projects/75458460/packages/pypi/simple/ wedolow-mcp-server-windows
```

{% endtab %}
{% endtabs %}

Replace `<your_token>` with the token which was sent to you to access the Beta.

{% hint style="warning" %}
If you previously installed WedoLow MCP Server from a .whl file (deprecated), please completely remove your virtual environment first, or run&#x20;
{% endhint %}

Everything is now installed to use Wedolow MCP Server on your system. Go to [Configuration section](/documentation/wedolow-mcp-server/server-configuration.md) to set it up.


---

# Agent Instructions: 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:

```
GET https://docs.wedolow.com/documentation/wedolow-mcp-server/server-installation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.