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.
- Windsurf with Devin Local, or the Devin CLI
- Team policies may require an administrator to enable or allowlist MCP access.
Connect Qwairy to Devin Local
1
Add the server
Add Qwairy at user scope:Use the root URL, without appending
/mcp.2
Sign in to Qwairy
3
Confirm the server
Legacy Cascade agent
For the legacy Cascade agent, open the MCP configuration file from the Cascade panel (… > Open MCP config file). Current versions store it at~/.config/devin/mcp_config.json on macOS and Linux and at %APPDATA%\devin\mcp_config.json on Windows. Older Windsurf versions used ~/.codeium/windsurf/mcp_config.json. Add Qwairy:
serverUrl or url for remote HTTP servers.
Check that the connection works
In the agent chat, send:list_brands tool and display the accessible brands. Approve the tool call if it asks. A general answer without a tool call does not confirm the connection.
Troubleshooting
The agent does not list Qwairy
Rundevin mcp get qwairy to check the server status. If your team manages Windsurf, ask an administrator whether MCP access is enabled and whether servers must be allowlisted.
The server is not found
Use the root URLhttps://mcp.qwairy.co without /mcp. For Cascade, check that mcp_config.json is valid JSON and restart Windsurf after editing it.
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
Commands, scopes, and team policies are maintained by Devin. See the Devin Local MCP guide and the legacy Cascade guide. Procedure checked against Devin’s documentation on August 28, 2026.Next steps
- Tools reference: what each Qwairy tool does
- Example conversations: prompts to try
- All supported clients

