Cursor Chat Bridge

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/udah1-cursor-chat-bridge

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

1 read · 4 write · 1 delete

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (6)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• bridge_awaitWait for the user's reply

  Blocks on this conversation's chat thread for a single long-poll window and returns JSON with status 'message' plus the reply text, 'timeout', or 'stopped'. Use it when you already posted with bridge_send and only need the answer; to post and wait together, prefer bridge_send_and_await. Replies are consumed as they are delivered, so each message comes back exactly once and a later call will not see it again. A 'timeout' is normal rather than an error — the window elapsed with no reply, and you keep waiting by calling again. 'stopped' means the user ended remote chat mode, so stop calling bridg…

• bridge_sendPost a message to the chat thread

  Posts one message to this conversation's chat thread and returns immediately without waiting for a reply. Use it for a progress note or a closing remark that needs no answer; when you need the user to respond, use bridge_send_and_await instead so the post and the wait are one call. Each call appends a new message and never edits or replaces an earlier one, so a retry after a failure leaves a duplicate in the thread.

• bridge_send_and_awaitPost a message and wait for the reply

  Posts a message to this conversation's chat thread and then blocks for the reply in one round trip — the end-of-turn summary-plus-question pattern, and the tool to reach for by default. Equivalent to bridge_send followed by bridge_await; use those separately only when you need to post and wait at different moments. Returns the same envelope as bridge_await: 'message' with the reply, 'timeout', or 'stopped'. The message is posted before the wait begins, so after a 'timeout' the user has already seen it — send only what is new rather than repeating the summary, which would post it twice.

• bridge_startStart remote chat mode

  Opens a dedicated thread for THIS conversation in the configured chat channel (GitHub issue, Telegram topic, or Discord channel) and returns the session handle that every other bridge_* tool requires. Call it when the user asks — in any language — to start remote chat, bridge, or Telegram mode. Call it once per conversation: every call without `session` opens a NEW thread, so re-arm an existing session by passing its handle back instead of starting again. When no channel is configured it returns onboarding instructions rather than failing, so follow them and call again. It identifies the conve…

• bridge_statusShow remote chat mode statusread-only

  Reports the bridge's record for THIS conversation as JSON — which adapter is in use, the thread it is bound to, and whether the session is still active — or a null session once it has ended. Diagnostics only: it posts nothing to the thread and does not consume a pending reply, so unlike bridge_await it is safe to call at any point, including while deciding whether a bridge_start is still needed. It answers from local daemon state without contacting the chat provider, so it confirms what the bridge believes rather than that the provider is reachable.

• bridge_stopEnd remote chat modecan change or delete data

  Ends remote chat mode for THIS conversation: the daemon stops polling the thread, any in-flight wait returns 'stopped', and the session handle stops working — resuming later needs a fresh bridge_start. The conversation history is left intact; the thread is not deleted and a GitHub issue is not closed, so the record stays readable afterwards. Calling it twice, or on a session that already ended, is harmless. Use it when the user says they are done — not in response to a 'timeout' from bridge_await, which only means no reply has arrived yet.

Signals

Stars

2

Forks

1

Open issues

1

Last commit

Aug 6, 2026 (2 months ago)

Last release

Aug 7, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.udah1/cursor-chat-bridge

Version

0.1.23

Auth

No auth

Packages

npm cursor-telegram-chat

License

MIT

Repository

github.com/udah1/cursor-chat-bridge

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql