Code Lens vs Skillmd
A side-by-side look at the Code Lens and Skillmd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Code Lens for developer tools work as a local process; choose Skillmd 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?
Choose Code Lens when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GEMINI_API_KEY, GOOGLE_API_KEY. - You want tools like
generate_diff, analyze_pr_impact, generate_review_summary.
Choose Skillmd when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- You want tools like
skillmd_search, skillmd_get, skillmd_install.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 47/100 · Fair | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GEMINI_API_KEYGOOGLE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 190 |
| Directory activity | 0 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 13 | 7 |
| Full listing | View Code Lens | View Skillmd |
Tools & capabilities
Code Lens tools 13
generate_diffCapture git diff (unstaged/staged) and cache server-sideanalyze_pr_impactAssess severity, categories, breaking changes, rollback complexitygenerate_review_summaryPR summary, risk rating, merge recommendationgenerate_test_planPrioritized test cases and coverage guidanceanalyze_time_space_complexityBig-O complexity analysis and degradation detectiondetect_api_breaking_changesDetect breaking API/interface changesload_fileCache a source file for analysis toolsrefactor_codeComplexity, duplication, naming, grouping suggestionsdetect_code_smellsStructural code smells (Fowler taxonomy)generate_documentationJSDoc/TSDoc/docstring stubs for public exportsask_about_codeNatural-language Q&A about a cached fileverify_logicVerify algorithms via Gemini code execution sandbox- +1 more on the listing page
Skillmd tools 7
skillmd_searchSearch the SkillMD registry of Agent Skills (SKILL.md files) by task, name or keywords. Returns matching skills with their owner/name slug, description, category, safety verdict and install snippet, best match first.skillmd_getFetch one skill by owner/name slug, including its SKILL.md body, provenance (source repo and pinned commit), license, safety verdict and capability flags.skillmd_installInstall a skill by owner/name slug: validates it, then writes one canonical copy (.agents/skills/<name>) and links it into the chosen agents' skill directories. Never executes scripts. The response reports the skill's capability flags (docs_only, network_calls, executes_scripts, reads_secrets) as information.skillmd_trendingTop skills on the SkillMD leaderboard, ranked by installs, saves and ratings, optionally within one category and time window.skillmd_recommendRecommend skills. With based_on set to a skill's owner/name slug, returns the top skills in that skill's category (excluding itself); without it, returns what is trending over the last 30 days.skillmd_list_savedList the signed-in user's saved skills. Requires the SKILLMD_TOKEN environment variable (a SkillMD personal access token).skillmd_lintValidate a SKILL.md against the SkillMD format and return diagnostics, capability flags and a 0-100 quality score. Pass raw SKILL.md content, or a registry slug (owner/name) to fetch and lint that skill.
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.
Code Lens
{
"mcpServers": {
"code-lens": {
"command": "npx",
"args": [
"-y",
"@j0hanz/code-lens-mcp@latest"
],
"env": {
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"GOOGLE_API_KEY": "YOUR_GOOGLE_API_KEY_HERE"
}
}
}
}
Skillmd
{
"mcpServers": {
"skillmd": {
"command": "npx",
"args": [
"-y",
"skillmds"
]
}
}
}
Frequently asked questions
Code Lens is categorized under Developer Tools and uses a local stdio subprocess. Skillmd belongs to Developer Tools and uses a local stdio subprocess. Pick Code Lens for developer tools work and Skillmd 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.
Code Lens has no declared pricing — check the project's own site. Skillmd 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 code-lens and skillmd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Code Lens has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Skillmd has 67/100 (Great) with 1 views, 0 installs and 190 GitHub stars.