About Luskad MCP
Luskad MCP connects MCP clients to project information and coding guidance in the Luskad app. It provides project listings and searchable project coding rules, with configuration through environment variables or command-line arguments.
Key features
- 01List available projects
- 02Search project coding rules
- 03Access project and team details
- 04Review progress, risks, and tasks
- 05Environment and CLI configuration
Use cases
- 01Look up coding standards for a project
- 02Retrieve project contacts and team information
- 03Review project status, risks, and tasks
MCP support
The MCP server exposes Luskad project data and coding rules as tools for MCP clients, including Cursor, Windsurf, VS Code, and Claude Desktop.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMELuskad MCP
A Model Context Protocol (MCP) server that provides access to coding rules and examples for your projects.
Features
- Project Management: Retrieve all available projects with their details
- Coding Rules: Search and access coding standards within specific projects
- Team Collaboration: Get team member information and project contacts
- Progress Tracking: Monitor project progress, risks, and tasks
- Feature Management: Access project features and their associated issues
- Flexible Configuration: Support for environment variables and command-line arguments
- Multi-Platform: Compatible with Cursor, Windsurf, VS Code, and Claude Desktop
Prerequisites
- Node.js (v16 or higher)
- npm or yarn
- Cursor, Windsurf, Claude Desktop or another MCP Client
You also need to create an account on luskad.com application and generate your API token.
Getting started
Install in Cursor
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Pasting the following configuration into your Cursor ~/.cursor/mcp.json file is the recommended approach. See Cursor MCP docs for more info.
{
"mcpServers": {
"Luskad": {
"command": "npx",
"args": ["-y", "@acmada/luskad-mcp"]
}
}
}
Install in Windsurf
Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
{
"mcpServers": {
"luskad": {
"command": "npx",
"args": ["-y", "@acmada/luskad-mcp"]
}
}
}
Install in VSCode
Add this to your VS Code MCP config file. See VS Code MCP docs for more info.
{
"servers": {
"luskad": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@acmada/luskad-mcp"]
}
}
}
Install in Claude Desktop
Add this to your Claude Desktop claude_desktop_config.json file. See Claude Desktop MCP docs for more info.
{
"mcpServers": {
"luskad": {
"command": "npx",
"args": ["-y", "@acmada/luskad-mcp"]
}
}
}
Available Tools
list-projects
Retrieves all available projects.
get-coding-rules
Search coding rules for a given project. Parameters:
projectId: Project to search for coding rulesquery: (Optional) Search query
Development
- Clone the repository:
git clone https://github.com/frocher/luskad-mcp.git
cd luskad-mcp
- Install dependencies:
npm install
- Build
npm run build
Configuration
Create a .env file in the root directory with the following variables:
API_URL=https://app.luskad.com/api/v1
API_KEY=<your api key>
Or provide the URL via command line:
node dist/index.js --url http://your-api-url --key <your api key>
Local configuration example
{
"mcpServers": {
"luskad": {
"command": "npx",
"args": [
"tsx", "/path/to/folder/luskad-mcp/src/index.ts",
"--url", "http://localhost:3000/api/v1",
"--key", "<your personal key>"
]
}
}
}
Testing with MCP Inspector
npx -y @modelcontextprotocol/inspector npx @acmada/luskad-mcp@latest
License
MIT License - see LICENSE for details.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.