Improve MCP server relevance and discoverability

[MarkSpectarium]

Tracking Issue - COMPLETED

All MCP server improvements have been implemented and merged to main.

Sub-Issues

Issue	Title	Status
#14	Add list_projects tool to MCP server	✅ Merged
#15	Add path filtering to find_relevant_files	✅ Merged
#16	Improve relevance scoring with path-based signals	✅ Merged
#17	Add path filtering to search_symbols	✅ Merged

Implementation Summary

list_projects (#14)

• Added list_projects MCP tool exposing KnowledgeBase.listProjects()
• Updated server.ts to pass dataDir to tool handler
• Commit: 876f1b1

excludePaths for find_relevant_files (#15)

• Added excludePaths parameter to find_relevant_files tool
• Files matching patterns are filtered before scoring
• Commit: e41600f

Path-based scoring (#16)

• SDK/vendor paths (SDK, Packages/, ThirdParty/, etc.) get -10 penalty
• Paths containing task keywords get +3 boost
• Commit: f94243e

pathFilter for search_symbols (#17)

• Added pathFilter parameter for directory scoping
• Only files with matching path prefix are searched
• Commit: f7c271a

Friction Notes (from agents)

• Worktrees require pnpm install before typecheck (expected)
• One Edit tool issue (dropped function brace) - quickly fixed

Verification

✅ All merges successful (no conflicts)
✅ pnpm typecheck passes
✅ pnpm build passes

Original Issue

See comment with original description.

[MarkSpectarium]

Original Issue Description (preserved)

Background

When using the MCP server for the first time to find "player death and respawn logic" in an indexed Unity project, several friction points were identified.

The issues below were found by the agent using it. Analyze them and verify that their suggested approach is correct. Then create individual issues for each with the correct prompts.
Then spawn agents in the right order to work on them.

Issues Found

1. No project discovery via MCP - Had to fall back to CLI to discover project name. Suggestion: Add list_projects tool.
2. find_relevant_files returns SDK/vendor noise - Top results were Metaplay SDK infrastructure files instead of actual game code. Suggestion: Add path-based filtering options.
3. Relevance scoring is purely keyword-count based - Files with many mentions score higher regardless of actual relevance. Suggestion: Improve scoring by deprioritizing SDK paths and boosting semantic path matches.
4. No path filtering on search_symbols - Would be useful to scope symbol searches to specific directories. Suggestion: Add optional pathFilter parameter.

Workaround

Using search_symbols with specific terms ("death", "respawn") was much more effective than find_relevant_files for this use case.