Connect Cursor

Cursor connects to a gateway through an entry in mcp.json. A person signs in with a gateway user. A setup that cannot open a browser sends an API key.

Before you begin

• A gateway that serves at least one API. See Create a gateway.
• A gateway user or an API key in the environment you connect to.

The configuration on this page is in the gateway's Connect tab, under Cursor, with your gateway's values filled in. For Cursor's own screens, see Model Context Protocol in the Cursor docs.

Add the gateway

Add the server to ~/.cursor/mcp.json to use it in every project, or to .cursor/mcp.json in a project to use it there. <gateway> is the name Cursor shows for the server. The portal uses the gateway's slug.

{
  "mcpServers": {
    "<gateway>": {
      "url": "https://gateway.faustine.ai/<workspace>/<gateway>/mcp"
    }
  }
}

{
  "mcpServers": {
    "<gateway>": {
      "url": "https://gateway.faustine.ai/<workspace>/<gateway>/mcp",
      "headers": {
        "Authorization": "Bearer <GATEWAY_KEY>"
      }
    }
  }
}

Make the first call

Ask Cursor's agent what it can do with the gateway, or ask for something the API returns, such as a list of contacts.

In the portal, the request appears in the gateway's Logs tab, and the Cursor card in the Connect tab shows when the client was last seen.

Cursor cannot ask the person for a confirmation. For an operation that requires one, the gateway refuses the call unless the credential is set to Run without asking. A new gateway user and a new API key both start on Refuse. See Confirmation.

Next steps

• Scope a key or user: limit what Cursor can call.
• Serving modes: Code and Tools: which tools the gateway gives Cursor.
• Connect clients: the other clients a gateway supports.