Analytics Legends — SAP Analytics Intelligence vs Repomix
A side-by-side look at the Analytics Legends — SAP Analytics Intelligence and Repomix MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
Analytics Legends — SAP Analytics IntelligenceDeveloper ToolsAI agent for SAP analytics: firms, day rates, contract radar, news, concepts, studies37FairAuth: not declaredVerdict: choose Analytics Legends — SAP Analytics Intelligence for developer tools work; choose Repomix for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose Analytics Legends — SAP Analytics Intelligence when
- You need dedicated capabilities in the Developer Tools domain.
Choose Repomix when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
pack_codebase, directory, compress.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A Analytics Legends — SAP Analytics Intelligence | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 64/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 28,979 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 23 |
| Full listing | View Analytics Legends — SAP Analytics Intelligence | View Repomix |
Tools & capabilities
Analytics Legends — SAP Analytics Intelligence tools
No tool names declared yet. Check the project README from the listing page.
Repomix tools 23
pack_codebasePackage a local code directory into a consolidated XML file for AI analysisdirectoryAbsolute path to the directory to packcompress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.attach_packed_outputAttach an existing Repomix packed output file for AI analysispathPath to a directory containing repomix-output.xml or direct path to a packed repository XML filepack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysisremoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.- +11 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.
Analytics Legends — SAP Analytics Intelligence
No confirmed install command for Analytics Legends — SAP Analytics Intelligence yet — follow the setup steps linked from its listing page rather than a guessed package name.
Repomix
{
"mcpServers": {
"repomix": {
"command": "npx",
"args": [
"-y",
"repomix@latest"
]
}
}
}
Frequently asked questions
Analytics Legends — SAP Analytics Intelligence is categorized under Developer Tools and uses an install path we have not confirmed yet. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick Analytics Legends — SAP Analytics Intelligence for developer tools work and Repomix for developer tools.
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. Analytics Legends — SAP Analytics Intelligence has no confirmed install command yet — follow its own setup instructions.
Analytics Legends — SAP Analytics Intelligence has no declared pricing — check the project's own site. Repomix has no declared pricing — check the project's own site. 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 analytics-legends-sap-analytics-intelligence and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Analytics Legends — SAP Analytics Intelligence has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 28,979 GitHub stars.