> 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/authentication-and-access.md).

# Authentication and access

How the Lineaje MCP server signs you in, and what your IDE can access.

## How sign-in works

The Lineaje-hosted MCP server uses OAuth. You don't copy tokens or API keys into your IDE.

1. The first time your IDE connects, it opens a browser window with the Lineaje **Application Access Request** page.
2. The page names the application asking for access and shows the address where your credentials will be sent. For desktop IDEs and CLIs, this is a `localhost` address on your own machine.
3. You click **Allow Access**, then log in to the Lineaje Portal with your existing credentials.
4. Your IDE stores the resulting token and uses it for later requests.

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FsUIbkCB4BebiTN56DkMn%2Fapp-access-request.png?alt=media&#x26;token=1846ac9f-25d0-4983-82f7-0a89878de068" alt="Lineaje application access request page"><figcaption></figcaption></figure>

{% hint style="warning" %}
Click **Deny** if you don't recognize the application named on the page, or if you didn't start the connection yourself.
{% endhint %}

<figure><img src="https://2983949833-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzRZpxg1UUX5iPuJAfelm%2Fuploads%2FYzXyDxzg4SB1vd4fKZMR%2Flogin-lineaje.png?alt=media&#x26;token=58c0b937-4635-4cfa-84bc-81eed01e224c" alt="Lineaje Portal login"><figcaption></figcaption></figure>

## What Allow Access grants

Allowing access lets your IDE call the Lineaje MCP tools on your behalf. The tools act as you: they see only the data your Lineaje account can see, and they can't do anything your account can't do.

## Tenant and organization scope

Every result is limited to your tenant and the organizations your account belongs to. To change which organizations you can see, an administrator updates your membership. See [Organization and User Management](https://docs.veedna.com/getting-started/organization-and-user-management.md).

## Licenses and tool visibility

| Tool                | License required |
| ------------------- | ---------------- |
| `sbom_search`       | SBOM360          |
| `security_workflow` | UnifAI           |

If your organization lacks the license for a product, that product's tool isn't available to you.

## Revoking access

To disconnect an IDE, remove the `Lineaje-MCP-Server` server from its MCP settings. From the command line:

* Claude Code: `claude mcp remove Lineaje-MCP-Server`
* OpenAI Codex: `codex mcp remove Lineaje-MCP-Server`

{% hint style="danger" %}
NEEDS INPUT: how long tokens stay valid, and whether a user or admin can revoke an IDE's access from the Lineaje Portal.
{% 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/authentication-and-access.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.
