> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/security-and-permissions.md).

# Security and permissions

How Supply'd protects your account and limits what an AI connection can read.

Supply'd MCP uses OAuth, the standard sign-in and authorisation flow used by modern connected apps. You sign in directly with Supply'd and choose the access you want to grant.

The connection is read-only and is limited by three layers:

1. the read-only MCP scope;
2. the business areas selected on the approval page; and
3. your current Supply'd user, company, location and store permissions.

A connection can never use MCP to obtain broader Supply'd access than the signed-in user already has.

## In this section

* [How sign-in works](/mcp/security-and-permissions/how-sign-in-works.md)
* [Permissions and privacy](/mcp/security-and-permissions/permissions-and-privacy.md)

{% hint style="warning" %}
Only approve a connection when the server is `https://mcp.supplyd.co/` and the Supply'd sign-in page is on `https://app.supplyd.co`.
{% 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://help.supplyd.co/mcp/security-and-permissions.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.