Cline connection throws status=error on resource and prompt template discovery queries

[ARZF]

Version

codebase-memory-mcp 0.9.0

Platform

Windows (x64)

Install channel

GitHub release archive / install.sh / install.ps1

Binary variant

standard

What happened, and what did you expect?

When an MCP client (Cline) connects to the codebase-memory-mcp server, it performs feature discovery by polling standard protocol endpoints. The server currently returns a hard error status code for endpoints it hasn't implemented, filling the console with error logs.

Instead of logging an explicit status=error, unimplemented lifecycle endpoints should gracefully return an empty list/array payload (e.g., []) or a formal JSON-RPC standard method-not-found response to prevent error spam in the host client console.

Reproduction

Any standard repository workspace. This issue is not codebase-specific; it occurs during the initial handshake / lifecycle discovery phase between the MCP client and the server across any project.

Logs

### Log Output

resources/list status=error duration_ms=0 
method=resources/templates/list status=error duration_ms=0 
method=prompts/list status=error duration_ms=0

Diagnostics trajectory (memory / performance / leak issues)

Project scale (if relevant)

No response

Confirmations

• I searched existing issues and this is not a duplicate.
• My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.

[DeusData]

Thanks for reporting this against 0.9.0. Triage: this is a MCP-client compatibility bug in discovery handling, especially visible with Cline. For the 0.9.1-rc train we should make unsupported resources/prompts discovery graceful: either a proper JSON-RPC method-not-found response without noisy local error logs, or empty-list responses where the MCP capability contract expects list methods to be harmless. Marking this high priority for the RC because it affects connection startup UX even when indexing itself is unrelated.

[ARZF]

Thanks for your response. I've rolled back to v0.8.1.I'll look forward to test the newer version.