Skip to main content
Qwairy works with Cursor as a remote MCP server. You add one entry to Cursor’s mcp.json, sign in with OAuth, and ask Cursor questions about your brands. The connection is read-only.

​
Before you start

  • Access to a Qwairy team on a Starter plan or higher. You can connect before monitoring has run. Queries return data once a live brand has generated responses.
  • Cursor installed and signed in
  • If your team manages Cursor, check that its policies allow MCP servers.

​
Connect Qwairy to Cursor

1

Add the server

Add Qwairy to ~/.cursor/mcp.json for a personal connection that works in every project. Use a project’s .cursor/mcp.json only when the server should be limited to that project.
Use the root URL, without appending /mcp.
2

Restart Cursor

Save the file and restart Cursor.
3

Sign in to Qwairy

Open Customize > MCPs, check that qwairy is enabled, and complete the OAuth sign-in. Sign in with the Qwairy account that has access to your brands and approve the access.

​
Check that the connection works

Open Cursor’s chat and send:
Cursor should call Qwairy’s list_brands tool and display the accessible brands. Approve the tool call if Cursor asks. A general answer without a tool call does not confirm the connection.

​
Troubleshooting

​
Qwairy does not appear in the MCP list

Check that the JSON in mcp.json is valid and that the file is in the right location. Restart Cursor after every edit.

​
The server is not found

Use the root URL https://mcp.qwairy.co without /mcp.

​
Authorization fails

Sign in with the Qwairy account that has access to your brands, and check that its team is on a Starter plan or higher. See general troubleshooting.

​
Official documentation

Interface labels and configuration options are maintained by Cursor. See Cursor’s MCP documentation. Procedure checked against Cursor’s documentation on August 28, 2026.

​
Next steps