@matifali added support for agentapi, do we still want to keep the support for coder_script in here ?

I think we should support 2 modes one where the session is interactive through AgnetAPi, the other un interactive session where the agent starts working with the first prompt there are options -p to support that.

I will let you choose if we need a coder_script here.

@matifali I had to add this line to readme

Cursor CLI dosen't seem fully compatible with MCPs, so Coder tasks and Coder MCP will not work with this module.

The cli executes the tool call and then just stops, and doesn't do any further processing. Have spent good amount of time trying to make this work, will keep an eye out for future releases and update it as needed.
Additionally it dosen't respect the env variable, had to find a hack to even make the tools discoverable.

@DevelopmentCats please give this a review, and let me know if it needs any other changes.

@35C4n0r I filed an issue and someone shared that having mcp.json works if it is in the same directory where the Cursor agent binary is run.

https://forum.cursor.com/t/cursor-cli-not-respecting-global-mcp-and-rules-configurations/129372

@matifali I had to add this line to readme

Cursor CLI dosen't seem fully compatible with MCPs, so Coder tasks and Coder MCP will not work with this module.

The cli executes the tool call and then just stops, and doesn't do any further processing. Have spent good amount of time trying to make this work, will keep an eye out for future releases and update it as needed. Additionally it dosen't respect the env variable, had to find a hack to even make the tools discoverable.

Did you try it the way that they recommend in the docs? I know the mcp servers work in cursor itself, and its labeled as supported in their docs.

MCP
Agent supports [MCP (Model Context Protocol)](https://docs.cursor.com/en/tools/mcp) for extended functionality and integrations. The CLI will automatically detect and respect your mcp.json configuration file, enabling the same MCP servers and tools that you’ve configured for the IDE.

https://docs.cursor.com/en/cli/using

Also the format for how mcp.json needs to be written is here https://docs.cursor.com/en/context/mcp

{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "mcp-server"],
      "env": {
        "API_KEY": "value"
      }
    }
  }
}

@DevelopmentCats yes, I've tried that, unfortunately neither does it respect the env, it also stops processing after the tool call, the same config, prompt and tool calls works perfectly fine with Cursor Desktop.

@35C4n0r I filed an issue and someone shared that having mcp.json works if it is in the same directory where the Cursor agent binary is run.

https://forum.cursor.com/t/cursor-cli-not-respecting-global-mcp-and-rules-configurations/129372

@matifali already figured this part out we are also using the folder/.cursor/mcp.json, from the screenshot in his comment I think he is using mcp.json in the project specific dir.
As of now, this:

stops processing after the tool call

is the only part that's keeping us from releasing this successfully.

@DevelopmentCats @matifali The tasks are running now with today's release 2025.08.15-dbc8d73, I've updated the Prompt and readme 🙌🏻

@matifali I've added the basic tftest. If we want to test this more thoroughly, we would have to update the agentapi module to output something (if this is something we want, let me know, I'll raise a separate PR to update the agentapi module.)