DEVELOPERS / MCP DOCUMENTATION
ChatGPT.
Meet OY1.
Add the OY1 plugin to ChatGPT for task memory and checks. Copy the setup prompt below to get started.
01 / CONNECT
plug me in
Copy, then paste into ChatGPT Work.
Computer · ChatGPT desktop app · Plus or higher
View prompt
Use Computer Use to open https://chatgpt.com/plugins and add OY1 (https://oylabs.ai/console?view=connect) with the MCP settings below. Reuse the existing connection if present. Enable Developer mode if needed. Pause for me to sign in or approve access. If Computer Use or custom MCP is unavailable, tell me what is missing. Start a new chat with OY1 selected. Call its oy_status tool and confirm the actual result before saying the connection works. Then help me start my first task. MCP: https://oylabs.ai/mcp · Authentication: OAuth. Select GPT-6 Astra High; tell me if unavailable. Turn Fast mode off if available.
Need help?
Enable Computer Use
Open Work → Plugins → Computer Use. Install it, enable both switches, then select Try now. Allow access when asked.
Availability varies by account and region. Setup help ↗
Using another AI app?
Add this address to an app that supports remote MCP with OAuth. Sign in to OY Labs, approve access, and enable OY1 in a new conversation. If asked for a transport, choose Streamable HTTP.
https://oylabs.ai/mcpName: OY1
Description: Task memory and checked workflows for your AI.
Authentication: OAuth
Ask the app to call OY1’s oy_status tool to check the connection.
Technical details
harness:read permits status, recall and planning. harness:run adds the task workflow. Your app obtains the required permissions through OAuth approval.
ChatGPT’s custom MCP connection requires the relevant developer features and workspace permission. The protocol and hosted endpoint have been tested; the end-to-end ChatGPT browser connection is still being validated. Availability and setup labels depend on the client.
02 / TOOL REFERENCE
Nine tools. One task.
Completed and cancelled tasks and their history are automatically deleted 90 days after closing. Unfinished tasks expire after 180 days without changes.
oy_status- Check the connection and available usage.
oy1_begin- Start with a goal and checkable success criteria. Returns a task ID and version.
oy1_propose- Record a hypothesis, next action and predictions before using an external tool.
oy1_observe- Report the prepared action’s observed, failed or uncertain outcome and compare it with predictions.
oy1_remember- Save a hypothesis, supported discovery or refuted idea with evidence from this task.
oy1_recall- Retrieve current state, memory, observed history and the next permitted step.
oy1_plan- Find a route to a previously observed state using unambiguous recorded transitions.
oy1_finish- Save the final answer after every success criterion has a passing check and no action is pending.
oy1_cancel- Close a task when the user asks to stop. This does not undo external actions.
Your client discovers the current input and output schemas through MCP tools/list. Write operations use the current expectedVersion and a unique operationId. After a lost response, retry the exact same arguments and operation ID within 24 hours; otherwise recall the state first.
03 / FIRST TASK
Make the check explicit.
Use OY1 to calculate three items at 17 plus 9 delivery. Check the total and whether it fits a budget of 65.
The expected total is 60, leaving 5. The client should begin with those two checks, propose a calculation, perform it, report the observation and finish only once both criteria are recorded as passing.
Run the complete worked example → Inspect the source, the recorded state changes and a deliberate prediction mismatch.
OY1 receives the tool arguments the client sends, including goals and reported observations. Send concise decisions and evidence, and only data you intend to store. See data handling and privacy.
04 / TROUBLESHOOTING
Get back to the task.
401: the connection is not authenticated
Reconnect through OAuth in your app’s connection settings. Sign in to OY Labs and approve the connection again.
403: insufficient permissions
Check that the connection has the scopes required by the tool. Running the workflow needs harness:run.
409: the task version changed
Call oy1_recall, read the current task state and continue with its version. Do not blindly repeat an external action.
A tool’s outcome is uncertain
Confirm the original action with a read-only check before resolving the same action ID. Repeating it could duplicate an external effect.
Opening the endpoint in a browser shows an error
The MCP endpoint is intended for protocol requests from a configured client. A normal browser page visit is not an authenticated MCP connection. Use the console connection settings.