# Cursor agent not picking up mcp.json from project - issue returned

**URL:** <https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576>\
**Category:** Bug Reports\
**Tags:** cli, mcp\
**Created:** [June 18, 2026, 3:30pm UTC](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576 "2026-06-18T15:30:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Dotsenko](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@Daniel\_Dotsenko](https://forum.cursor.com/u/Daniel_Dotsenko)\
**Post date:** [June 18, 2026, 3:30pm UTC](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576/1 "2026-06-18T15:30:40Z")

</div>

### Where does the bug appear (feature/product)?

Cursor CLI

### Describe the Bug

Cursor agent not picking up mcp.json from project

This is a return of [Cursor agent not picking up mcp.json from project](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project/157026)

Cursor CLI v 2026.04.08-a41fba1 had this solved. That version CLI reliably detects `./.cursor/mcp.json` file (per project file relative to CWD)

Cursor CLI v 2026.06.15-18-00-12-6f5a2cf is broken again. This version CLI does NOT auto-detect the `./.cursor/mcp.json` file (per project file, relative to current working dir).

in `2026.06.15-18-00-12-6f5a2cf ` `/mcp list` shows no servers and it does not ask how to initiate the agent with or without MCP on the start, unlike 2026.04.08-a41fba1 which does.

Contents of `./.cursor/mcp.json` :

```auto
{
  "mcpServers": {
    "data_catalog": {
      "type": "streamable-http",
      "url": "http://amundsenmetadata:5000/mcp"
    }
  }
}

```

### Steps to Reproduce

see description

### Expected Behavior

that newer versions of Cursor CLI agent work as well as older versions and detect project-level MCP json file.

### Operating System

Linux

### Version Information

Cursor CLI v 2026.04.08-a41fba1 had this solved. That version CLI reliably detects `./.cursor/mcp.json` file (per project file relative to CWD)

Cursor CLI v 2026.06.15-18-00-12-6f5a2cf is broken again. This version CLI does NOT auto-detect the `./.cursor/mcp.json` file (per project file, relative to current working dir).

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [June 18, 2026, 4:02pm UTC](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576/5 "2026-06-18T16:02:00Z")

</div>

Hi @Daniel_Dotsenko!

> [@Daniel\_Dotsenko](#):
>
> ```auto
> "type": "streamable-http",
> 
> ```

Could you try removing this line (or changing `type` to `http`) and see if if it works?

> [@Cursor-agent mcp list silently drops entire mcp.json when any entry has type: "streamable-http" (works in IDE)](https://forum.cursor.com/t/cursor-agent-mcp-list-silently-drops-entire-mcp-json-when-any-entry-has-type-streamable-http-works-in-ide/158521):
>
> Where does the bug appear (feature/product)? Cursor CLI Describe the Bug cursor-agent mcp list silently drops entire mcp.json when any entry has type: “streamable-http” (works in IDE) Summary cursor-agent silently drops the entire mcp.json when any single entry uses "type": "streamable-http" — including unrelated stdio entries in the same file. The Cursor editor accepts streamable-http as an alias; the CLI only accepts http / sse / stdio. Users with a working IDE config hit a silent break the …

---

<div class="post-metadata">

**Author:** ![Daniel\_Dotsenko](https://avatars.discourse-cdn.com/v4/letter/d/ee7513/32.png) [@Daniel\_Dotsenko](https://forum.cursor.com/u/Daniel_Dotsenko)\
**Post date:** [June 19, 2026, 1:51pm UTC](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576/7 "2026-06-19T13:51:07Z")

</div>

Yes, changing

```auto
{
  "mcpServers": {
    "data-catalog": {
      "type": "streamable-http",
      "url": "http://amundsenmetadata:5000/mcp"
    }
  }
}

```

to

```auto
{
  "mcpServers": {
    "data-catalog": {
      "type": "http",
      "url": "http://amundsenmetadata:5000/mcp"
    }
  }
}

```

I am guessing the spec changed in the last half a year? (`streamable-http` as value was recommended by AI ~4 months ago).

I cannot find a published spec for this. I bet there are others with similar older config. Would be nice if Cursor would publish the schema with valid values for the `mcp.json` file content

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [June 19, 2026, 3:04pm UTC](https://forum.cursor.com/t/cursor-agent-not-picking-up-mcp-json-from-project-issue-returned/163576/10 "2026-06-19T15:04:22Z")

</div>

@Daniel_Dotsenko We should most likely just update the CLI to discard the `type`, or accept `streamable-http` as an alias for `http`! We have a bug ticket open for this.