Connect Cursor

Before you start

Cursor is a good option if your team already uses Cursor MCP and your Cursor setup supports remote MCP. An Enginy admin just needs to enable the MCP integration for the workspace — that’s it to get started. Enginy grants full access by default; restricting policy scopes is an optional, advanced step for later.

Add the hosted server

Cursor reads hosted MCP servers from mcp.json. Add an enginy entry to .cursor/mcp.json for a project-level setup:

{
  "mcpServers": {
    "enginy": {
      "url": "https://openapi.enginy.ai/mcp"
    }
  }
}

You can also place the same entry in ~/.cursor/mcp.json for a global setup. After restarting Cursor or refreshing MCP servers, let Cursor open the browser flow and approve Enginy.

Verify the connection

After authorization, ask Cursor to use Enginy MCP and run:

mcp_whoami

That confirms the hosted MCP server is reachable, OAuth completed, and the granted scopes match what Enginy approved.

Client support matrix

Compare support levels and setup shapes across every Enginy MCP client.

Security and troubleshooting

Debug auth, scope, token, and transport issues after Cursor connects.

Getting started

Clients

Guides

Reference

Before you start

Add the hosted server

Verify the connection

Client support matrix

Security and troubleshooting

​Before you start

​Add the hosted server

​Verify the connection

Client support matrix

Security and troubleshooting

Before you start

Add the hosted server

Verify the connection