Endpoint
Configuration
Cursor / Claude Desktop
Add the following to your MCP client configuration:Debug Mode
For local development, enable debug auth by settingMCP_DEBUG_AUTH=true:
Available Tools
Once connected, external MCP clients can use these tools:desktop_exec
Execute shell commands on the user’s local machine.- File operations:
ls,cat,mkdir,mv,cp,rm,find,grep - Version control:
git status,git add,git commit,git push - Package management:
npm install,pip install,brew install - Programming:
python,node, etc.
browser_read
Silently extract data from browser pages.text- Get page or element text contenttable- Extract table data (returns 2D array)form- Get form field values (key-value pairs)screenshot- Page screenshot (base64 PNG)html- Get HTML sourceurl- Get current page URL
hitl_prompt
Request input from the end user (for verification codes, confirmations, etc.).- SMS/email verification codes
- User confirmation dialogs
- Dynamic information requests
list_workflows
List all published workflow tools on the Desktop.name- Tool name (prefixed withworkflow_)description- Tool descriptioninputSchema- Input parameters JSON Schema
execute_workflow
Execute a published workflow tool.check_desktop_status
Check if the Desktop App is connected.Authentication
The MCP Gateway supports two authentication methods:JWT tokens are issued by Better Auth and validated using JWKS with 1-hour cache.
Architecture
Example: Using Zeus in Cursor
- Generate an API token from Zeus Web UI
- Configure Cursor’s MCP settings
- In Cursor, ask Claude to: