MCP server
Connect ChatGPT, Claude, Claude Code, Codex or another assistant to mgmtOS for Labels, then read records and review changes.
The mgmtOS for Labels MCP server lets compatible assistants find workspace records, explain product features and prepare changes for your review. mgmtOS hosts the server; you do not need to run its backend yourself.
Server URL: https://label.mgmtos.io/mcp
Use a client below and an mgmtOS for Labels account with access to the intended workspace. The connection uses OAuth in your browser. A Help Center or support chat session alone does not grant access to workspace records.
Choose the instructions for ChatGPT, Claude, Claude Code, Codex or another client below and add https://label.mgmtos.io/mcp.
Follow the sign-in link to mgmtOS for Labels. Use the account that belongs to the intended workspace.
Check the account, workspace, artist access and requested permissions on the consent page.
Approve the access you intend to grant, then return to your assistant.
Start with a read-only request before asking it to change a record.
mgmtOS for Labels is not yet published in the ChatGPT Plugins Directory. Connect its MCP server directly in Developer mode; there is no catalog install button yet. This direct connection is separate from submitting a plugin to OpenAI for publication.
In ChatGPT, open Settings → Security and login and turn on Developer mode.
Open ChatGPT Plugins, select the plus button, and enter mgmtOS for Labels as the connection name.
Under Connection, choose the public endpoint option and enter https://label.mgmtos.io/mcp, including the
/mcppath.Create the connection and review the tools and metadata discovered from mgmtOS for Labels.
Start a new conversation, open its tools menu, and add the mgmtOS for Labels MCP connection.
When ChatGPT asks to connect your account, complete mgmtOS for Labels OAuth in the browser. Check the account, workspace, artist access and requested permissions before approving.
Developer mode availability depends on your ChatGPT account and workspace policy. OpenAI's current documentation does not promise it for a fixed list of plans. If the setting or plus button is absent, your current account or workspace does not allow adding this unpublished MCP server; mgmtOS for Labels cannot enable that ChatGPT control.
In a managed workspace, administrators can also limit MCP availability and actions through Workspace apps and Permissions & roles. These controls do not expand your mgmtOS for Labels permissions.
After connecting, start with a read request. ChatGPT can only use the workspace access and scopes you approve. To end mgmtOS for Labels access, revoke the grant from Settings → Connected assistants in mgmtOS for Labels; removing a ChatGPT-side connection alone does not undo work already committed in mgmtOS for Labels.
Add mgmtOS for Labels as a custom connector using its server URL. This setup does not depend on a listing in Claude's connector directory.
Open Customize → Connectors in Claude. On an individual Pro or Max account, choose + → Add custom connector.
Enter mgmtOS for Labels as the name where requested and https://label.mgmtos.io/mcp as the remote server URL, then add it.
Choose Connect and complete the mgmtOS for Labels sign-in and permission review. You do not need to enter an API key or a client secret for this setup.
In your Claude conversation, open + → Connectors and enable mgmtOS for Labels before asking a question about your workspace.
For Team or Enterprise, an owner first adds the custom web connector under Organization settings → Connectors → Add → Custom → Web. Members then connect it with their own mgmtOS for Labels accounts. Availability and organization controls belong to your Claude plan.
Add the remote server from your terminal:
claude mcp add --transport http labelos https://label.mgmtos.io/mcp
Open Claude Code and run:
/mcp
Select mgmtOS for Labels, complete authentication in the browser, and check the account, workspace and requested access before approving. Return to Claude Code and try a read request.
Use Codex's native HTTP connection. Run these commands in your terminal:
codex mcp add labelos --url https://label.mgmtos.io/mcp
codex mcp login labelos
The login command starts browser authorization. Approve the intended mgmtOS for Labels workspace and permissions, then return to Codex.
If you manage configuration directly, add this server entry to your Codex configuration and run the same login command:
[mcp_servers.labelos]
url = "https://label.mgmtos.io/mcp"
Use codex mcp list to check that the server is configured. A saved configuration alone does not mean OAuth sign-in has completed.
For a client with native remote MCP and OAuth support, choose its HTTP server option and enter https://label.mgmtos.io/mcp. Complete the browser sign-in when prompted.
For a desktop client that only starts local MCP commands, use the mcp-remote bridge. Node.js and npm must be available to the client process.
| Setting | Value |
|---|---|
| Command | npx |
| Arguments | -y mcp-remote https://label.mgmtos.io/mcp |
| Environment | None |
If the client accepts a mcpServers JSON configuration, use:
{
"mcpServers": {
"labelos": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://label.mgmtos.io/mcp"]
}
}
}
Save the configuration, start or reload the server in your client, and complete the browser authorization. This bridge runs locally; npx -y can install the package automatically. No mgmtOS for Labels credentials belong in the environment settings. If your client uses a different configuration format, copy the command and arguments into its equivalent fields.
A connection uses your current workspace membership, role, artist scope and applicable workspace access. An assistant cannot expand that access by asking for it.
General records, contacts, financial information, files and administration have separate permission scopes.
A grant lasts up to 90 days and can be revoked earlier.
A record or action outside your current access remains unavailable through the assistant.
Use a specific record or question. Replace Night Drive with the release you want to inspect.
Find the release Night Drive. Show its open tasks, their owners and due dates. Follow every result page so the list is complete. Do not change anything.
For a product explanation, try:
Explain the difference between release status and readiness in mgmtOS for Labels. Link to the relevant guide.
Workspace search covers releases, artists, contacts and tasks within your access. Product guidance comes from the help corpus; reading actual workspace records is a separate permissioned operation.
Changes to workspace records begin with a preview. The preview does not change the business record.
Ask the assistant to read the current record.
Describe one concrete change and ask for a preview.
Check the named record, proposed values and effects before proceeding.
Read Night Drive and prepare a preview to move its release date to 2026-10-02. Show the current date, proposed date and any consequences. Wait for my review before applying it.
The intent expires after ten minutes and is tied to the current connection, actor and record revisions.
Some changes require an additional signed-in review. These include deletions, financial writes, administrative changes, and changes to release date, artist, lifecycle status or planning hold.
Open the review link returned by the assistant.
Confirm the affected record and every proposed change.
Approve that exact intent in mgmtOS for Labels if it is correct.
Return to the assistant and ask it to commit the reviewed intent.
Check the saved result and the record's history.
Commit the exact preview I approved in mgmtOS for Labels. Then read Night Drive again and confirm its saved release date.
Approval and commit are separate steps. Approving the review page does not itself apply the change.
If the intent expires or a referenced record changes, use a fresh read and preview. An earlier approval does not cover different data.
Read the latest Night Drive record and prepare a new preview for the same requested date. Explain what changed since the previous preview and wait for a new review.
After committing, inspect the returned result and the record's history.
Check the file and its destination before asking an assistant to upload it. Uploading stores the file before it is attached to a record.
Identify the file and the release or task it belongs to.
Ask the assistant to upload it and verify the completed file size and checksum.
Review the later attachment change before it is committed.
Files up to 10,000,000 bytes can use resumable chunks. Uploaded CSV, XLS and XLSX files support the same limit. Workbook processing also checks expanded size and sheet dimensions; an oversized workbook is rejected instead of partially imported.
Open Connected assistants, also available from Settings.
Find the assistant and review its granted permissions.
Choose its revoke action and confirm when you want to end access.
The connection-management page remains available when a subscription has stopped. Revocation ends future access through that grant; it does not undo committed work.
Provider connection setup can require a separate signed-in product flow. Follow the returned link and complete that flow yourself. Subscription purchases and billing management are available only in the mgmtOS for Labels web app, not through MCP.
For a date change, keep the handoff explicit:
Read: inspect Night Drive and its current release date.
Preview: propose the exact new date without applying it.
Review: inspect and approve the named intent in mgmtOS for Labels.
Commit: ask the assistant to apply that approved intent.
Verify: check the saved date, related deadlines and change history.