MCP OAuth: CIMD Support Plans and Timelines

Ideas Feature Requests
1

Feature request for product/service

Chat

Describe the request

Hello team,

The latest MCP specification v.2025-11-25 states the following: ”MCP clients and authorization servers SHOULD support OAuth Client ID Metadata Documents as specified in OAuth Client ID Metadata Document.”

Other popular Agents/IDEs (e.g. VS Code, Claude Desktop) have already added the CIMD support.

Could you please share the plans and timelines for supporting CIMD for MCP authorization by Cursor IDE? Lacking the feature blocks users from connecting to the MCP servers that require user authorization and don’t support DCR.

Thank you!

Operating System (if it applies)

Windows 10/11
MacOS
Linux

6 Likes
2

Hey, thanks for the feature request.

Right now, Cursor supports OAuth for MCP servers via Dynamic Client Registration (DCR) and static credentials. For servers without DCR, you can use a static config in mcp.json:

{
  "mcpServers": {
    "server-name": {
      "url": "https://api.example.com/mcp",
      "auth": {
        "CLIENT_ID": "your-client-id",
        "CLIENT_SECRET": "your-client-secret",
        "scopes": ["read", "write"]
      }
    }
  }
}

More details in the docs: Model Context Protocol (MCP) | Cursor Docs

About CIMD, I’ll pass the request to the team. There isn’t a specific timeline for this feature yet.

3

Thank you, Dean, for the quick reply. The information about the static credentials support is helpful.

We would appreciate it if you could share the feedback from the team regarding the timelines for CIMD support.

3 Likes
4

+1 on CIMD support.

Pretty please :slightly_smiling_face:

1 Like
5

+1 for CIMD support, DCR does not scale and doesn’t allow for good security practices.

1 Like
6

+1, please prioritize support for CIMD. CIMD is the default and without support, it completely blocks my customers from using Cursor with my company’s MCP server.

2 Likes
7

+1 My customers are large enterprises (some in regulated industries) and CIMD is their preferred approach, over DCR

8

+1 for supporting this. We have to switch back to VS Code anytime we want to use Storybook’s MCP (which uses CIMD for auth) :frowning:

9

Adding a vote for CIMD support! DCR is a no-go for us for security reasons.

1 Like
10

+1000 for CIMD support! My company’s MCP offering can’t be used within Cursor without this!

11

Claude has now added support for CIMD so cursor is one of the biggest holdouts for us to disable our DCR