# We need Cursor to support OAuth flow for remote MCP servers

**URL:** <https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719>\
**Category:** Feature Requests\
**Created:** [May 14, 2025, 10:32am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719 "2025-05-14T10:32:37Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![vittorius](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/vittorius/32/7160_2.png) [@vittorius](https://forum.cursor.com/u/vittorius)\
**Post date:** [May 14, 2025, 10:32am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/1 "2025-05-14T10:32:37Z")

</div>

Basically, the subject.

OAuth is the only MCP-native auth protocol that is [defined](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization) in the specification. Vendors release new MCPs that are SSE-only and thus cannot be configured via an API key. And, using OAuth is more secure than the API key that has to be stored plaintext in the mcp.json config.  
So, we’re losing this competition so far.  
How it looks like in Claude: [https://youtu.be/w-w37LWNcIk?t=88](https://youtu.be/w-w37LWNcIk?t=88)

So please, please, prioritize this auth approach support.

---

<div class="post-metadata">

**Author:** ![condor](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/condor/32/73148_2.png) [@condor](https://forum.cursor.com/u/condor)\
**Post date:** [May 14, 2025, 10:36am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/2 "2025-05-14T10:36:51Z")

</div>

Yeah, this will be needed by many servers soon. Passing an API key in URL like some MCP providers do now is not safe.

---

<div class="post-metadata">

**Author:** ![jacob\_dietle](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jacob_dietle/32/55241_2.png) [@jacob\_dietle](https://forum.cursor.com/u/jacob_dietle)\
**Post date:** [May 17, 2025, 8:06pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/3 "2025-05-17T20:06:39Z")

</div>

Yeah this makes a ton of sense especially given the roll out of these servers (all using OAuth):

> **[MCP Demo Day: How 10 leading AI companies built MCP servers on Cloudflare](https://blog.cloudflare.com/mcp-demo-day/)**
>
> We’re teaming up with Anthropic, Asana, Atlassian, Block, Intercom, Linear, PayPal, Sentry, Stripe, and Webflow to launch new remote MCP servers, built on Cloudflare, to enable Claude users to manage projects, generate invoices, and even deploy...

I tried to get the linear mcp server working, it crashes out since it cannot complete the flow

---

<div class="post-metadata">

**Author:** ![omerfe](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/omerfe/32/60862_2.png) [@omerfe](https://forum.cursor.com/u/omerfe)\
**Post date:** [June 4, 2025, 11:11am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/4 "2025-06-04T11:11:37Z")

</div>

Hey Cursor team when do we get the oAuth support on Cursor client? It’s the recommended way in the spec and should be prioritized rn

---

<div class="post-metadata">

**Author:** ![nhalstead](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/nhalstead/32/61122_2.png) [@nhalstead](https://forum.cursor.com/u/nhalstead)\
**Post date:** [June 5, 2025, 5:47am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/5 "2025-06-05T05:47:13Z")

</div>

It was released in the latest change log: [MCP one-click install and OAuth support](https://www.cursor.com/changelog#mcp-one-click-install-and-oauth-support).

---

<div class="post-metadata">

**Author:** ![sbosio](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/sbosio/32/61285_2.png) [@sbosio](https://forum.cursor.com/u/sbosio)\
**Post date:** [June 5, 2025, 2:09pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/6 "2025-06-05T14:09:56Z")

</div>

@nhalstead we’re working on Streamable HTTP servers with OAuth 2.0 DCR and we’re having issues with Cursor’s OAuth dynamic client registrations. It seems to be using redirect URIs with a private (native app) URI scheme that doesn’t follow RFC 7595, Section 3.8 recommendations: [RFC 7595 - Guidelines and Registration Procedures for URI Schemes](https://datatracker.ietf.org/doc/html/rfc7595#section-3.8).

Some OIDC-compliant Authorization Servers strictly validate the URI scheme for native apps and expect it to use the domain name, expressed in reverse order, for security reasons (avoiding collisions and providing identification on the scheme owner), which doesn’t seem to be the case for Cursor.

Is there any reason why Cursor isn’t following the IETF recommendation. Are there any provisions in place to support this moving forward? We just want to know this to plan accordingly on patching our Authorization Server implementation to relax this security setting and allow for any URI scheme string (or at least add the one Cursor uses to a sort of allow list).

Best!

---

<div class="post-metadata">

**Author:** ![Ashwin\_Jeksani](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ashwin_jeksani/32/69478_2.png) [@Ashwin\_Jeksani](https://forum.cursor.com/u/Ashwin_Jeksani)\
**Post date:** [July 2, 2025, 2:11am UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/7 "2025-07-02T02:11:40Z")

</div>

@nhalstead We’re encountering a scenario where the MCP server tools require specific scopes, and these are correctly exposed via the /.well-known/oauth-protected-resource endpoint as `scopes_supported`. However, Cursor doesn’t seem to pick them up or include them in the generated Authorization URL inspite to missing scopes error. Could you take a look and see if this can be addressed?

---

<div class="post-metadata">

**Author:** ![ThomSMG](https://avatars.discourse-cdn.com/v4/letter/t/54ee81/32.png) [@ThomSMG](https://forum.cursor.com/u/ThomSMG)\
**Post date:** [July 28, 2025, 2:50pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/8 "2025-07-28T14:50:53Z")

</div>

So [https://api.githubcopilot.com/mcp/](https://api.githubcopilot.com/mcp/) does not work with OAuth. [They note](https://github.com/github/github-mcp-server/tree/efef8ae27a1d62c38c8f760ca38a65845efd3576/docs/installation-guides#installation-guides-by-host-application):

> **Note:** Remote MCP support requires host applications to register a GitHub App or OAuth app for OAuth flow support – even if the new OAuth spec is supported by that host app. Currently, only VS Code has full remote GitHub server support.

---

<div class="post-metadata">

**Author:** ![A\_V](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@A\_V](https://forum.cursor.com/u/A_V)\
**Post date:** [November 4, 2025, 7:13pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/9 "2025-11-04T19:13:32Z")

</div>

I am able to complete the oauth flow successfully in MCP inspector but the same MCP server does not work in Cursor. My MCP server adheres to MCP Authorization spec and returns oauth-protected-resource url correctly with 401 response but doesn’t return any json body. I see following errors in Cursor

```auto
2025-11-04 11:08:25.339 [error] Client error for command HTTP 401: Invalid OAuth error response: SyntaxError: Unexpected end of JSON input. Raw body: 
2025-11-04 11:08:25.347 [error] Error connecting to streamableHttp server, falling back to SSE: HTTP 401: Invalid OAuth error response: SyntaxError: Unexpected end of JSON input. Raw body: 

```

Does MCP client in Cursor expect a json body in 401 response? OR am I misinterpreting the logs and this is a red herring?

---

<div class="post-metadata">

**Author:** ![Thijs\_de\_Vries](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/thijs_de_vries/32/88670_2.png) [@Thijs\_de\_Vries](https://forum.cursor.com/u/Thijs_de_Vries)\
**Post date:** [November 26, 2025, 8:53pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/10 "2025-11-26T20:53:19Z")

</div>

I was able to get oauth working in cursor. I needed the .well-known endpoint as well as the registration endpoints as well as making sure the mcp endpoint at 401 error. Previously I had allowed the listing of tools even if not authenticated and only authenticated on tool calls since that is how the library I was using worked. Adding the check for the `Authorization` header and doing a 401 if it wasn’t set before doing any calls to the mcp fixed the issue.

```ruby
# Not needed for claude code but needed for cursor. Without
# the 401 cursor wouldn't prompt for authorization.
# Rack renames Authorization to HTTP_AUTHORIZATION. Depending
# on your programming language you may need something different.
unless request.headers["HTTP_AUTHORIZATION"]
  render json: {error: "unauthorized"}, status: 401
  return
end

# Old code which is still needed but under the 401 guard clause
server = MCP::Server.new(
  # other values,
  server_context: {
    authorization: request.headers["HTTP_AUTHORIZATION"]
  }
)

render json: server.handle_json(request.body.read)

```

---

<div class="post-metadata">

**Author:** ![bug](https://avatars.discourse-cdn.com/v4/letter/b/fbc32d/32.png) [@bug](https://forum.cursor.com/u/bug)\
**Post date:** [December 20, 2025, 12:40pm UTC](https://forum.cursor.com/t/we-need-cursor-to-support-oauth-flow-for-remote-mcp-servers/91719/11 "2025-12-20T12:40:01Z")

</div>

Still not being able to have cursor to call the authentication endpoint. it comes up with all kind of suggestion for mcp.json that don’t work. discovery and DCR work fine with MCP inspector. my MCP and OAUTH2 server is on localhost.
