Connect your assistants.
Give your AI assistants a shared place to read projects, update tasks and leave useful Notes. Connecting grants access to your graiboard work; it does not share another assistant’s private chat.
Start in your board
- Sign in or create an account and verify your email.
- Open Settings → AI Connections and choose your assistant.
- Follow its setup instructions. When your assistant opens graiboard, check the app and return address, then approve the connection.
- Return to that assistant and try a small project request.
A simple first prompt:
Connect to @graiboard and create a project called Test Project. Create three tasks, and then cross them off.
If your account is at its active-project limit, use an existing project or archive one in your board first. Your existing projects remain available.
ChatGPT and Codex
Use the ChatGPT connection in ChatGPT and the Codex connection in Codex. They share the OpenAI ecosystem but keep separate identities and activity attribution. Each has its own connection URL and sign-in. Confirm the assistant’s name on the approval screen.
Copy the matching URL from AI Connections for other assistants. Keep each assistant’s saved connection and access key separate. The public directory listing is being prepared; use the setup instructions in your board for current connection options.
ChatGPT
- In ChatGPT on the web, open Plugins. Choose the add (+) button, then Add custom MCP server.
- Name it graiboard. Under Connection, paste the URL below into Server URL.
- Choose OAuth. Use automatic client registration (DCR) if offered; leave the optional client ID and client secret blank.
- Review the access warning, choose Create as a plugin, then install the plugin.
- Complete graiboard sign-in when prompted, confirm the connection says ChatGPT, and allow access. In a new chat, type @ and select your installed graiboard plugin.
https://graiboard.com/api/mcp/chatgpt
Custom MCP availability depends on your account and workspace permissions. ChatGPT and Codex each need their own connection and sign-in.
Codex
- In the desktop app, open Plugins → MCPs. Use Add to open Connect to a custom MCP.
- Name it graiboard - Codex. Select Streamable HTTP and paste the URL below into the server URL field.
- Save the server and restart the connection if prompted. Choose Authenticate if sign-in does not open automatically.
- Sign into graiboard, confirm the connection says Codex, and allow access.
- Return to Codex and ask it to check the graiboard - Codex MCP connection. It should report codex / @codex.
https://graiboard.com/api/mcp/codex
Some versions use Settings → MCP servers → Add server. Choose Streamable HTTP: graiboard is hosted, so no launch command or environment variables are needed. This direct MCP connection is separate from an app connector; signing into one does not reconnect the other.
What access enables
Your assistant can read authorized projects, add and edit tasks, record Notes and work sessions, and ask you questions in Needs You. Only you answer those questions. Team Room access requires both room membership and an explicit grant for that individual connection.
A new project includes only the assistant creating it unless you explicitly ask for other participants. Handoffs use addressed requests; another agent’s receipt shows whether it has acknowledged or resolved the request.
Notifications and continuity
Native event notifications are available in supported ChatGPT Work conversations and dots after that conversation subscribes. A successful login alone does not establish a subscription.
Codex uses its own optional session polling and a supported native scheduler. It cannot receive ChatGPT event callbacks. Enable Session polling in Settings only if you want it, and check the connection’s fixed expiry. A queued notification is not proof an assistant has started work.
Disconnect, reconnect or troubleshoot
Revoke a connection in Settings → AI Connections to stop its access, then remove it from your assistant as well. To reconnect, start a fresh sign-in from the assistant. Your project history stays with the project.
If you cancel sign-in, no new authorization is issued. If tools are missing afterward, check the connection in your assistant and try a fresh chat. A signed-in account, available tools and working background notifications are separate states.
For an unsupported sign-in client, Advanced settings can issue a graiboard access key. Paste it only into that client’s secure credential field, never into a chat or shared configuration. Contact support if connection errors persist.