Serena mcp selection
Rules for selecting between the LSP and JetBrains Serena MCP servers when both are configured. Default to LSP unless the user explicitly opts in to JetBrains.From its SKILL.md
npx -y skills add ceilidhboy/skills --skill serena-mcp-selectionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.0 KB, 173 tokens by cl100k_base, as published. Nobody here has run it
Serena MCP Server Selection
Rule
When both Serena (LSP) and Serena (JetBrains) MCP servers are available, always default to LSP unless the user explicitly tells you to use the JetBrains backend.
Guidance
- Use
mcp({ server: "Serena (LSP)", ... })for all routine code navigation, editing, and search. - Only switch to
mcp({ server: "Serena (JetBrains)", ... })when the user says something like "use the JetBrains version", "switch to JetBrains", or otherwise explicitly opts in. - JetBrains may be useful for deep sessions on a single project where the IDE is open alongside the agent. It is not robust for multi-project workflows.
- There is no auto-detection or fallback logic. The user chooses.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most mcp tooling skills give in 173 tokens
Counted across 638 of the 750 authors here whose files we hold, read 2026-08-07
- Create ten complex or independent read-only evaluation questionsin 69 of 638, across 15 files
- Test servers using MCP Inspectorin 61 of 638, across 19 files
- Provide actionable error messages with specific next stepsin 54 of 638, across 12 files
- Prioritize comprehensive API coverage over specific workflows or workflow toolsin 54 of 638, across 12 files
- Use TypeScript and Streamable HTTP for remote servers or clientsin 54 of 638, across 8 files
- Define structured output schemas where possiblein 50 of 638, across 8 files
- Use Zod or Pydantic for input schemasin 47 of 638, across 5 files
- Fetch MCP specification pages with markdown suffixin 46 of 638, across 4 files
- Load framework documentation using WebFetchin 45 of 638, across 3 files
- Verify each evaluation answer independentlyin 45 of 638, across 3 files
- Implement API client with authentication and paginationin 45 of 638, across 3 files
- Define input schemas with validationin 27 of 638, across 9 files
Said here and by no other author read
- Default to the LSP server
- Use LSP for routine code navigation, editing, and search
- Switch to the JetBrains server only when the user explicitly opts in
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.