# MCP headers config ignored when server has OAuth discovery

**URL:** <https://forum.cursor.com/t/mcp-headers-config-ignored-when-server-has-oauth-discovery/156054>\
**Category:** Bug Reports\
**Tags:** mcp\
**Created:** [March 27, 2026, 4:11pm UTC](https://forum.cursor.com/t/mcp-headers-config-ignored-when-server-has-oauth-discovery/156054 "2026-03-27T16:11:18Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 15, 2026, 12:49pm UTC](https://forum.cursor.com/t/mcp-headers-config-ignored-when-server-has-oauth-discovery/156054/10 "2026-04-15T12:49:55Z")

</div>

@Ayaz_Khan - I passed this along to the team. The regression after upgrading to v3 is a useful signal for prioritization. Unfortunately, there’s no client-side workaround right now. The logic to skip OAuth when the `Authorization` header is present is simply missing.

@chris-NR7 - this is the same bug. I already replied in your separate thread here: [Regression: github projects endpoint no longer accessible - #5 by deanrie](https://forum.cursor.com/t/regression-github-projects-endpoint-no-longer-accessible/157261/5)

If anything changes or a fix ships, we’ll update here.

---

_[View the full topic](https://forum.cursor.com/t/mcp-headers-config-ignored-when-server-has-oauth-discovery/156054)._