Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Huly MCP ServerCreate a new high priority issue to fix the login page bug"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Huly MCP Server
Custom MCP server for Huly workspace built from scratch. Runs on your remote server and connects to Huly WebSocket API.
Features
✅ Built from scratch - No dependencies on buggy
huly-mcppackage✅ Fixes all bugs - Correct
attachedToClass,collection, andkindfields✅ Auto-resolves project kind IDs - Automatically gets correct task type for each project
✅ Runs on remote server - Deploy on your server where Huly is hosted
✅ Connects via SSH - Cursor connects via SSH to remote server
Installation on Remote Server
cd /path/to/huly-mcp-server
npm install
npm run buildConfiguration
Create .env file or set environment variables:
HULY_URL=https://workspace.teasersoftware.com
HULY_EMAIL=your-email@example.com
HULY_PASSWORD=your-password
HULY_WORKSPACE=Teaser Software
PORT=3000Running the Server
On Remote Server
npm start
# or for development
npm run devThe server uses stdio transport (standard MCP protocol).
Connecting from Cursor
For HTTP Server (Remote)
Add to Cursor Settings → MCP Servers:
{
"mcpServers": {
"huly-remote": {
"url": "http://your-server-ip:3000/mcp",
"env": {
"HULY_URL": "https://workspace.teasersoftware.com",
"HULY_EMAIL": "your-email@example.com",
"HULY_PASSWORD": "your-password"
}
}
}
}For Stdio Server (Local)
{
"mcpServers": {
"huly-local": {
"command": "node",
"args": ["/absolute/path/to/huly-mcp-server/dist/index.js"],
"env": {
"HULY_URL": "https://workspace.teasersoftware.com",
"HULY_EMAIL": "your-email@example.com",
"HULY_PASSWORD": "your-password"
}
}
}
}How It Works
Connects to Huly: Uses WebSocket API to connect to your Huly workspace
Resolves Project IDs: Automatically converts project names to space IDs
Gets Correct Kind ID: Queries existing issues to get the correct task type ID for each project
Creates Issues Correctly: Sets all fields correctly:
attachedToClass: "tracker:class:Issue"collection: "subIssues"kind: <project-specific-id>
Available Tools
create_issue- Create issues with correct fieldslist_issues- List issues from projectslist_projects- List all projects
Development
npm run dev:http # Run HTTP server in development
npm run dev # Run stdio server in development
npm run build # Build TypeScriptDeployment on Remote Server
1. Copy to Server
scp -r huly-mcp-server user@your-server:/opt/huly-mcp-server2. Install and Build
ssh user@your-server
cd /opt/huly-mcp-server
npm install
npm run build3. Create .env File
cat > .env << EOF
HULY_URL=https://workspace.teasersoftware.com
HULY_EMAIL=hha.nguyen298@gmail.com
HULY_PASSWORD=Ha@29082002
HULY_WORKSPACE=Teaser Software
EOF4. Test Locally on Server
node dist/index.js
# Should see: "Huly MCP Server running on stdio"The server is ready! Cursor will connect via SSH.