list-projectsLABSCO SUMMARY
House style the assistant can look up instead of guess.
Coding conventions only bind if they are reachable at the moment code is written. Pointing the assistant at the project's rules turns "we do it this way here" from something you paste every session into something it queries.
What it is
A server in front of Luskad, where a team keeps its coding rules and examples. The assistant lists the projects it has access to and searches the rules inside one, so the standards it writes against are the ones your team wrote down rather than its own defaults.
What you get
- All available projects retrieved with their details
- Coding rules searched within a named project, with an optional query
- Configuration by environment variable or command-line argument
- The same npx package across Cursor, Windsurf, VS Code and Claude Desktop
Requirements
Node.js v16 or higher with npm or yarn, and an account at app.luskad.com with a generated API token. The client runs it with npx -y @acmada/luskad-mcp, so nothing is cloned.
Setup effort
One command plus a key — npx -y @acmada/luskad-mcp, then supply credentials
USE CASES
Pointing the assistant at the right rulebook
List the projects available under your token and pick the one this repository belongs to.
Checking the convention before writing the code
Search the project's rules for naming, error handling or testing, and write against what comes back.
Reviewing a change against house style
Pull the rules covering the area being changed, so review comments cite the standard rather than a preference.
2 tools
Listed in project docs. Your client may show a different list.
get-coding-rulesBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js
- API_KEY in your environment
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
npx -y @acmada/luskad-mcpMCP Clients
Cursor
{
"mcpServers": {
"Luskad": {
"command": "npx",
"args": [
"-y",
"@acmada/luskad-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>"
}
}
}
}<YOUR_API_KEY> is the API token generated in your luskad.com account.
Windsurf, Claude Desktop
{
"mcpServers": {
"luskad": {
"command": "npx",
"args": [
"-y",
"@acmada/luskad-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>"
}
}
}
}<YOUR_API_KEY> is the API token generated in your luskad.com account.
VS Code
{
"servers": {
"luskad": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@acmada/luskad-mcp"
],
"env": {
"API_KEY": "<YOUR_API_KEY>"
}
}
}
}<YOUR_API_KEY> is the API token generated in your luskad.com account.