Lousa vs MCP Adr Analysis Server
A side-by-side look at the Lousa and MCP Adr Analysis Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Lousa for data visualization work as a local process; choose MCP Adr Analysis Server for data visualization as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Lousa when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PORT, HOST, LOUSA_DATA_DIR, LOUSA_BUCKET, LOUSA_TOKEN, LOUSA_URL, LOUSA_DEFAULT_TTL_HOURS. - You want tools like
create_board, update_board, get_board.
Choose MCP Adr Analysis Server when
- You need dedicated capabilities in the Data Visualization domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
PROJECT_PATH, ADR_AGGREGATOR_API_KEY, HTTP_PROXY, HTTPS_PROXY. - You want tools like
analyze_project_ecosystem, get_architectural_context, generate_adrs_from_prd.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Data Visualization | Data Visualization |
| Quality signal | 51/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | PORTHOSTLOUSA_DATA_DIRLOUSA_BUCKETLOUSA_TOKENLOUSA_URLLOUSA_DEFAULT_TTL_HOURS | PROJECT_PATHADR_AGGREGATOR_API_KEYHTTP_PROXYHTTPS_PROXY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 35 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 5 | 63 |
| Full listing | View Lousa | View MCP Adr Analysis Server |
Tools & capabilities
Lousa tools 5
create_boardCreates a board from a scene, returns `{id, url}update_boardReplaces the scene; unchanged elements stay byte-identical so only changes animateget_boardRead boardsget_selectionWhat the user selected in the viewer (ids + full elements)delete_boardDeletes a board
MCP Adr Analysis Server tools 63
analyze_project_ecosystemComprehensive recursive project ecosystem analysis with advanced prompting techniques (Knowledge Generation + Reflexion)get_architectural_contextGet detailed architectural context for specific files or the entire project, automatically sets up ADR infrastructure if missing, and provides outcome-focused workflow for project successgenerate_adrs_from_prdGenerate Architectural Decision Records from a Product Requirements Document with advanced prompting techniques (APE + Knowledge Generation)compare_adr_progressCompare TODO.md progress against ADRs and current environment to validate implementation statusanalyze_content_securityAnalyze content for sensitive information using AI-powered detection with optional memory integration for security pattern learninggenerate_content_maskingGenerate masking instructions for detected sensitive contentconfigure_custom_patternsConfigure custom sensitive patterns for a projectapply_basic_content_maskingApply basic content masking (fallback when AI is not available)validate_content_maskingValidate that content masking was applied correctlymanage_cacheManage MCP resource cache (clear, stats, cleanup)configure_output_maskingConfigure content masking for all MCP outputssuggest_adrsSuggest architectural decisions with advanced prompting techniques (Knowledge Generation + Reflexion). TIP: Read @.mcp-server-context.md first for project history, patterns, and previous ADRs to ensure consistency.- +51 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Lousa
{
"mcpServers": {
"lousa": {
"command": "npx",
"args": [
"-y",
"lousa"
],
"env": {
"PORT": "YOUR_PORT_HERE",
"HOST": "YOUR_HOST_HERE",
"LOUSA_DATA_DIR": "YOUR_LOUSA_DATA_DIR_HERE",
"LOUSA_BUCKET": "YOUR_LOUSA_BUCKET_HERE",
"LOUSA_TOKEN": "YOUR_LOUSA_TOKEN_HERE",
"LOUSA_URL": "YOUR_LOUSA_URL_HERE",
"LOUSA_DEFAULT_TTL_HOURS": "YOUR_LOUSA_DEFAULT_TTL_HOURS_HERE"
}
}
}
}
MCP Adr Analysis Server
{
"mcpServers": {
"tosin2013-mcp-adr-analysis-server": {
"command": "npx",
"args": [
"-y",
"mcp-adr-analysis-server"
],
"env": {
"PROJECT_PATH": "YOUR_PROJECT_PATH_HERE",
"ADR_AGGREGATOR_API_KEY": "YOUR_ADR_AGGREGATOR_API_KEY_HERE",
"HTTP_PROXY": "YOUR_HTTP_PROXY_HERE",
"HTTPS_PROXY": "YOUR_HTTPS_PROXY_HERE"
}
}
}
}
Frequently asked questions
Lousa is categorized under Data Visualization and uses a local stdio subprocess. MCP Adr Analysis Server belongs to Data Visualization and uses a local stdio subprocess. Pick Lousa for data visualization work and MCP Adr Analysis Server for data visualization.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Lousa has no declared pricing — check the project's own site. MCP Adr Analysis Server is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add lousa and tosin2013-mcp-adr-analysis-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Lousa has a quality signal of 51/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MCP Adr Analysis Server has 67/100 (Great) with 2 views, 0 installs and 35 GitHub stars.