grok-agent-threads
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
grok-agent-threads
From your phone, ask Grok Bot (or ChatGPT, Codex, or any other agent that speaks MCP) about your Claude Code chats and Codex threads on your Mac, and have it message them:
"list my pinned Claude chats" "what does my launch chat need from me?" "message my launch chat: where are we?" "start a Codex thread in my vault called Weekly review and ask it to draft the outline"

The agent gets the same reach into your chats that a Claude chat has from inside the Claude app. It sees the same titles, sidebar groups and status lines, it can read and search every conversation, and it can message any chat, open or closed, and get the answer back. It can also start new chats in the folder you name, and do all of the same with Codex threads.
Nothing on your Mac is exposed to the internet. The server listens on 127.0.0.1 only, and your tailnet reaches it through tailscale serve. A cloud agent like Grok Bot joins your tailnet through Tailscale's official OAuth app sign-in.
Tools
Tool | What it does |
| Your Claude Code chats as the Claude app sidebar shows them, newest first. Each row has the title, whether the chat is open (busy or idle) or closed, last activity, group, pinned, and the chat's own one-line status or what it needs from you. Filter by title words, group or pinned |
| Your sidebar groups, with how many chats each holds |
| One chat in full: state, status, what it needs from you, folder, model, turns, link |
| A chat's last messages, each labeled by who wrote it: you, the relaying agent, another session, or the chat |
| Searches every conversation's full history |
| Messages any chat and returns its answer. An open chat answers in place. A closed chat wakes up with its own folder, model, permission mode and settings |
| Starts a new chat in a folder, names it, adds it to the Claude app sidebar, and returns its first answer and link. New chats start in auto mode |
| Says whether closed and new chats run live in the Claude app right now or in the background, and what brings live mode back |
| Your Codex threads, newest first. Takes an optional search |
| A Codex thread's last turns |
| Messages a Codex thread and returns the answer. A thread the ChatGPT app has open gets the message through its queue |
| Starts a named Codex thread in a folder |
There is no tool to delete, archive or stop a chat or thread, on purpose.
Related MCP server: Claude Codex Computer Use
Seeing the work
In the Claude app. A chat that is open in the app answers in place, live. A closed or new chat runs live too when the relay chat is open: one small chat inside the app that asks the app to wake the target (docs/relay.md). Without the relay, closed and new chats work in the background and show the result when you open them.
In a browser, anywhere on your tailnet. Every result that says "still working" carries a private watch link, and
chat_statusgives one for any chat. The page streams the chat's messages and steps as they happen, on your phone or your Mac, whichever way the turn runs.
Install
By prompt (recommended). Paste docs/install-prompt.md into Claude Code on your Mac. Claude checks what you have, installs the server as a login item shared on your tailnet only, tests it, starts the relay chat, and hands you the setup prompt for your agent with your address filled in.
By hand. You need macOS, Claude Code (the Claude desktop app is optional), uv, ripgrep, and the Tailscale app signed in. Codex is optional; its tools turn on when the ChatGPT app or the codex CLI is installed.
git clone https://github.com/ArtemXTech/grok-agent-threads ~/grok-agent-threads
cd ~/grok-agent-threads
scripts/install.sh "Your Name" "Grok Bot" # your name, and the agent that will call it
uv run scripts/check.py # tools, status and your newest chatsinstall.sh keeps the server running as a login item on 127.0.0.1:8857, shares it on your tailnet with tailscale serve (never Funnel), creates an access key, and prints the address with it, for example https://your-mac.your-tailnet.ts.net:8857/mcp?key=.... scripts/install.sh --uninstall removes both.
Connect your agent.
Grok Bot: paste docs/grok-setup-prompt.md into Grok Bot with your address filled in. Grok connects its Tailscale plugin (you click once to sign in), adds the server, and runs a full test.
Any other MCP client: add the address (with its
?key=) as a streamable HTTP MCP server. On the same Mac you can use stdio instead:uv run --directory ~/grok-agent-threads grok-agent-threads --stdio.Live work in the Claude app: start the relay chat once (docs/relay.md). The install prompt does it for you.
Settings
All settings are environment variables. scripts/run.sh passes them through, and scripts/install.sh writes them into the login item.
Variable | Default | Meaning |
|
| Your name, used in the note on every relayed message |
|
| The agent that calls the server |
| set by | Access key every MCP request must carry ( |
|
| Port on |
| set by | Extra Host headers to accept (your tailnet name). Any other Host is refused |
|
| Seconds a call waits for an answer before it reports "still working" (the work goes on) |
|
| Permission mode for |
|
| Where every call is logged ( |
Security
Read docs/security.md before you connect a cloud agent. In short:
Who can reach it: only devices on your tailnet that also have your access key (the installer makes one). The Grok Bot device joins with your identity, so it can also reach your other devices. To prevent that, give it a tag and allow that tag only this port; the doc has a ready policy.
What the agent can do: whatever your chats can do. A closed chat wakes up in its own permission mode, which can mean edits and commands on your Mac without a prompt.
What a chat is told: every relayed message opens with a note. It says who typed the words and that they are never your approval for anything outward (sending, posting, paying).
Your words only: tell your agent to pass along only words you typed. The setup prompt does this.
How it works
See docs/how-it-works.md, including which parts rely on documented interfaces and which rely on app internals that an update could move.
Tests
uv run --group dev pytestThe tests run against synthetic data in a temporary home folder and never touch your real chats.
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Search, read, and write your Apple Notes from ChatGPT/Claude via a local Mac agent + MCP relay.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Your AI apps as one team: hand work to Codex or Claude Code on your Mac, with a shared logbook.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceThe self-hosted MCP bridge between Claude Chat and Claude Code.46AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceAn unofficial bridge that lets Claude Code control local macOS applications through an existing OpenAI Computer Use installation by launching the signed Codex client and translating MCP compatibility.68 npm14MIT
- AlicenseNot gradedqualityBmaintenanceEnables local discovery, reading, and messaging between running Codex and Claude Code sessions through MCP.216 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables voice assistants to start, monitor, message, and approve local Claude Code sessions on your computer, including sessions already open in a terminal. It exposes session management, recaps, approvals, and history search as MCP tools.7GPL 3.0