LabscoMCP early access ↗
tuncer-byteMCP SERVER

CURSOR25X

Keeps a Cursor session in an interactive loop: it waits for your next instruction in the terminal instead of ending the turn.

by tuncer-byte ↗Notifications & Alerting to HumansCommunity

LABSCO SUMMARY

One tool, and the point is that it does not return.

Normally an assistant finishes a turn and waits for the chat box. Here the tool call stays open and reads from a terminal, so a sequence of small instructions runs as one continuous session. Whether that suits you depends on how you work — it means the terminal, not the chat pane, becomes where you type. Everything happens in the detected workspace directory, so check which one it resolved before the first run.

What it is

A single-tool MCP server for Cursor IDE. Starting it creates a small input script and a Cursor rules file, then holds a loop that reads your typed instruction, processes it, and comes back for the next one.

What you get

  • start_task_loop is the one tool — it starts the loop and keeps it running
  • It creates cursor25xinput.cjs for terminal input and .cursor/rules/cursor25x.mdc for the loop's rules on first run
  • Input is classified into create, read, update, delete and help, with results returned before the loop waits again
  • Typing stop ends the loop cleanly
  • The working directory is resolved from CURSOR_WORKSPACE, then PWD, then a default cursor25x folder in your home directory

Requirements

Node.js and a checkout, built with npm install and npm run build, then registered in ~/.cursor/mcp.json pointing at dist/index.js. Nothing to authenticate. It is written for Cursor IDE specifically — the rules file it generates is Cursor's format.

Setup effort

Build from source — git clone https://github.com/tuncer-byte/cursor25x.git

See installation options