Context OS / Setup guide
Connect your tools
Read your saved project context from ChatGPT, Codex or Claude.
The public directory listings are being prepared. Until a listing is published, use a supported custom MCP connection or an installation package supplied by Context OS. Availability of custom connections depends on your tool and plan.
Before you connect
- Sign in to Context OS and create a project or accept access to an existing one.
- Save useful project context: what you are working on, current decisions and the next action.
- For an organization project, confirm explicit project access. Joining the organization alone does not grant access to every project.
- Review our privacy policy and current retention and deletion controls. Information returned to an AI tool is also processed under that provider’s terms and settings.
Connect with OAuth
- In your tool, install the Context OS package or add a custom remote MCP connection using
https://context-os.online/api/mcp. - Choose OAuth authentication when prompted. The server supports discovery, dynamic client registration and PKCE. Do not paste your Context OS access token into a conversation.
- Sign in to the intended Context OS account. Customer sign-in uses an emailed code. Directory reviewers use the dedicated reviewer sign-in link and credentials supplied privately.
- Review the requested permissions. The first directory package uses read access to context; it cannot save changes, approve requests or delete projects.
- Complete the connection and ask: “Show the projects I can access in Context OS.”
Try a useful question
Choose a project from the returned list and ask: “What is the current state, what is blocked, and what should I do next? Cite the saved documents.” You can also ask why a decision was made or request a specific document. The answer should distinguish saved facts from plans and include source references when the tool provides them.
If something is missing
- No projects: check the connected account and its explicit project memberships. Save context in the project before requesting a bundle.
- Access denied: request access from the project owner. Reconnecting cannot grant additional permissions.
- Connection expired: reconnect through your tool’s connection settings. Reviewer access may also have reached its stated deadline.
- You expected automatic memory: an MCP connection retrieves saved cloud context. It does not capture conversations or install local hooks. Follow the separate session-memory setup guide to opt in on supported desktop workflows.
Disconnect
Open Connections in Context OS, find the authorized app and revoke its connection. Revocation stops future access through that grant; it does not erase information already returned to the tool. You can also remove the connection in the tool itself.
Need help? Contact [email protected]. Include the tool name, error message and approximate time. Never send passwords or tokens.