> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/lineaje-mcp-server/self-hosted-deployment.md).

# Self-hosted deployment

Run the Lineaje MCP server in your own cloud environment.

## When to self-host

Most teams use the Lineaje-hosted server at `https://mcp.v2.prod.veedna.com/mcp`. Self-host when your policies require MCP and scan traffic to stay inside your own cloud environment, for example in a UnifAI hybrid deployment.

## Deploy on Azure

The self-hosted server runs on an Azure Linux VM with Docker Compose, with Caddy handling TLS on port 443. For requirements, network allowlists, and step-by-step setup, see [Deploy UnifAI on Azure](https://docs.veedna.com/unifai/setting-up/deploy-unifai-on-azure.md).

## Point your IDE at a self-hosted server

A self-hosted server differs from the hosted one in two ways:

* Use your server's address instead of the hosted URL: `https://<FQDN>/mcp`. Keep the `/mcp` path.
* Sign in with a bearer token in the `Authorization` header instead of the browser flow. Store the token in your IDE's secret storage or an environment variable, and never commit it to a repository.

For IDE configuration examples, see Connect an MCP client on the Azure page.

{% hint style="danger" %}
NEEDS INPUT: which tools a self-hosted server exposes. Confirm whether `sbom_search` is available, or only UnifAI tools.
{% endhint %}


---

# 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.veedna.com/lineaje-mcp-server/self-hosted-deployment.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.
