@cristian-adam said in MCP Server and Warp Terminal, Connection Issue:

We also have now an ACP Client

wait what? okay how do i use that? do you mean i can open a chat window from inside Qt Creaor and then talk to all the LLMs provided by my Cursor subscription?

Yes. All the https://agentclientprotocol.com/get-started/registry would be able to talk to Qt Creator.

if so, how do i do that? note i do not compile Qt nor Qt Creator, i'm expecting to just 'update' like i normally do

yes? please?

We have Qt Creator 20 snapshots. No need to compile Qt Creator. Enable the ACP Client plugin, go to Settings > AI > ACP Servers and then configure Cursor. You would have to figure out the Launch command and the Launch arguments.

The UI is far from final 😅

We also have now an ACP Client

wait what? okay how do i use that? do you mean i can open a chat window from inside Qt Creaor and then talk to all the LLMs provided by my Cursor subscription?
if so, how do i do that? note i do not compile Qt nor Qt Creator, i'm expecting to just 'update' like i normally do

yes? please?

钟勇
After testing, it turned out that the real reason is quite simple: VSCode does not support MCP servers using the SSE protocol.
However, it does support HTTP. Therefore, I had Copilot write a proxy (Streamable HTTP ↔ SSE), and now VSCode can interact with QtCreator normally.

VS Code uses the Streamable HTTP protocol (sending requests via POST and receiving results in the HTTP response body), while Qt Creator uses the SSE protocol (establishing an event stream via GET, sending requests via POST, and receiving responses asynchronously through the SSE stream).

What the proxy does:

On startup: Establishes a persistent SSE connection with Qt Creator, with a background thread continuously reading the event stream and routing responses to the corresponding waiters based on their id.

When receiving a POST request from VS Code:

Parses the JSON-RPC message and extracts the id.

Forwards it to Qt Creator (POST /sse).

If there is an id (it's a request): Blocks and waits for the response with the matching id in the SSE stream, then returns it as the HTTP response body to VS Code.

If there is no id (it's a notification): Forwards it directly and returns a 202.

When receiving a GET request from VS Code: Provides an SSE stream and forwards notifications actively pushed by Qt Creator.

In short: VS Code [Streamable HTTP] ↔ Proxy ↔ [SSE] Qt Creator

Alternatively you can try Qt Creator 20 snapshots. In Qt Creator 20 we rewrote the network connection part. We also have now an ACP Client that allows you to chat with any of these ACP compatible agents e.g. Claude Agent, Cursor, Codex CLI, or OpenCode.

Lastly Thank you @davecotter for the initial work with the mcp server plugin. Without this we wouldn't have all of this. 🙏

    "qt-creator": {
      "url": "http://localhost:3001",
      "transport": "http"
    },