> 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/manage-your-connection/availability-and-beta-limitations.md).

# Private beta availability and limits

Access requirements, usage cost and current boundaries for the Supply'd MCP private beta.

Supply'd MCP is not yet generally available. It is offered by invitation to selected Supply'd ERP customers as a read-only private beta.

## Product availability

| Supply'd product | MCP availability                      |
| ---------------- | ------------------------------------- |
| Supply'd ERP     | Private beta access by invitation     |
| Supply'd Hub     | Not available as a standalone product |
| Supply'd Lite    | Not available as a standalone product |

A user who also uses Hub or Lite as part of a Supply'd ERP account connects through their ERP account and ERP permissions. Hub or Lite access by itself does not qualify for MCP access.

## Usage cost

Each MCP server call uses **0.01 Supply'd usage tokens**.

* 1 server call uses 0.01 usage tokens.
* 10 server calls use 0.1 usage tokens.
* 100 server calls use 1 usage token.

One AI question may make multiple server calls. For example, the client may first search for a product and then make another call to retrieve its recipe or production history. The total usage therefore depends on the number of calls required, not simply the number of questions asked.

MCP usage counts toward the Supply'd usage allowance associated with the ERP account. Any subscription or usage charges from your AI provider are separate.

## Current boundaries

* The connection reads authorised Supply'd ERP information; it does not perform actions.
* Available business areas depend on your Supply'd ERP plan, company configuration, selected access and user permissions.
* Custom connectors may depend on your AI provider's plan and workspace administrator settings.
* ChatGPT is the primary tested client. Claude and other standards-compatible remote MCP clients may also connect, but their interface and support can vary.
* Large results are bounded and may require a narrower follow-up question.

## During the private beta

Capabilities, field coverage, pricing and client compatibility may change as feedback is incorporated. After a significant capability update, refresh or rescan the client's tool catalogue and approve updated definitions. Reconnecting may be required if the client cannot refresh them.

The read-only boundary will remain explicit. Any future action that changes Supply'd ERP data will require separate documentation, permissions and confirmation safeguards before it is made available.

## Feedback

When reporting a problem, include the question you asked, the expected result, the client used and the time it occurred. Do not include passwords or access tokens.

See [Troubleshooting](/mcp/manage-your-connection/troubleshooting.md) for the information that helps Support investigate safely.


---

# 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/manage-your-connection/availability-and-beta-limitations.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.