Cursor Setup
Early Access
Try our newest feature! Only available through reach out. Contact us to join the early access program and get priority support.
Prerequisites
- Cursor IDE
- Unizo API key and Identity integration ID
- Node.js v20 or higher
Setup Instructions
-
Install @mcp-remote if not already installed:
npm i mcp-remote
-
Open Cursor Settings (
Cmd/Ctrl + ,
) -
Add MCP configuration:
- macOS/Linux
- Windows
Navigate to Cursor's settings.json and add:
{
"mcpServers": {
"unizo-identity": {
"command": "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/node",
"args": [
"/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/mcp-remote",
"http://api.unizo.ai/mcp/identity",
"--allow-http",
"--header",
"apikey:${UNIZO_API_KEY}"
],
"env": {
"UNIZO_API_KEY": "your_api_key"
}
}
}
}
{
"mcpServers": {
"unizo-identity": {
"command": "npx",
"args": [
"mcp-remote",
"http://api.unizo.ai/mcp/identity",
"--allow-http",
"--header",
"apikey:${UNIZO_API_KEY}"
],
"env": {
"UNIZO_API_KEY": "your_api_key"
}
}
}
}
- Restart Cursor to load the MCP server
Flags: If npx is producing errors, consider adding -y as the first argument to auto-accept the installation of the mcp-remote package.
{
"mcpServers": {
"unizo-identity": {
"command": "/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/node",
"args": [
"-y",
"/Users/{user_name}/.nvm/versions/node/v18.x.x/bin/mcp-remote",
"http://api.unizo.ai/mcp/identity",
"--allow-http",
"--header",
"apikey:${UNIZO_API_KEY}"
],
"env": {
"UNIZO_API_KEY": "your_api_key"
}
}
}
}
Available Tools
Once configured, you'll have access to:
list_users
- Browse and search users across identity systemsget_user_details
- Retrieve comprehensive user informationlist_groups
- Explore groups, roles, and permissionsmanage_group_members
- Add or remove users from groupscheck_permissions
- Analyze and validate user access rightsaudit_access
- Review authentication logs and security events
Environment Variables
You can also set environment variables in your shell profile:
- macOS/Linux
- Windows
export UNIZO_API_KEY = "your_api_key"
[System.Environment]::SetEnvironmentVariable("UNIZO_API_KEY", "your_api_key", "User")
Then reference them in settings.json:
{
"env": {
"UNIZO_API_KEY" : "${env:UNIZO_API_KEY}",
}
}
Multiple Integrations
Configure multiple identity providers:
{
"mcpServers": {
"unizo-identity": {
"command": "npx",
"args": [
"mcp-remote",
"http://api.unizo.ai/mcp/scm",
"--allow-http",
"--header",
"apikey:${UNIZO_API_KEY}"
],
"env": {
"UNIZO_API_KEY": "your_api_key"
}
},
"unizo-ticketing": {
"command": "npx",
"args": [
"mcp-remote",
"http://api.unizo.ai/mcp/ticketing",
"--allow-http",
"--header",
"apikey:${UNIZO_API_KEY}"
],
"env": {
"UNIZO_API_KEY": "your_api_key"
}
}
}
}
Troubleshooting
MCP not detected
- Check Cursor's output panel: View → Output → MCP
- Ensure Node.js v20+ is installed
Authentication errors
- Verify your API key in Unizo dashboard
- Check that the integration ID is correct
- Ensure the integration is active
Debug mode
Enable debug logging in settings.json:
{
"args": [
"--debug"
]
}