Move aggregation to mcpd-proxy and add resource templates support (#4)

* Refactor to use SDK methods and add resource templates support

* Simplified all MCP protocol handlers to use SDK client methods instead of manual fetch calls. This provides automatic health checking, 501 Not Implemented handling, concurrent requests, caching, and proper error handling.

* Added missing resource templates support via ListResourceTemplatesRequestSchema handler.

* Removed all console output to keep stderr clean for MCP stdio protocol. Removed unnecessary try/catch blocks that just re-throw errors.

* Move server aggregation from SDK to proxy

* Version updates

* Bump to JS SDK v0.0.2

* Use mcpd-proxy version 0.0.2

* Fix generate prompt

* Update README

* Use vi.mocked

Author: peteski22

README.md

@@ -16,10 +16,10 @@ An MCP (Model Context Protocol) server that acts as a proxy between IDEs and the
 
 ## Features
 
-- Unified Interface: Single MCP server exposing all `mcpd`-managed tools
+- Unified Interface: Single MCP server exposing all `mcpd`-managed capabilities
 - Tool Aggregation: Tools from all servers with `server__tool` naming convention
-- Resource Support: Access resources from all servers with `mcpd://` URIs
-- Prompt Support: Aggregate prompts from all servers
+- Resource Aggregation: Resources from all servers with `server__resource` naming and `mcpd://` URIs
+- Prompt Aggregation: Prompts from all servers with `server__prompt` naming convention
 - Efficient Caching: Leverages SDK caching for health checks and tool schemas
 - Zero Configuration: Works out of the box with sensible defaults
 - TypeScript: Built with `TypeScript` for type safety
@@ -181,9 +181,11 @@ mcpd-proxy/
 │   └── apiPaths.ts            # API endpoint constants
 ├── tests/
 │   └── unit/                  # Unit test files
+│       ├── aggregation.test.ts
 │       ├── apiPaths.test.ts
 │       ├── config.test.ts
-│       └── parsers.test.ts
+│       ├── parsers.test.ts
+│       └── server.test.ts
 ├── .github/
 │   └── workflows/             # GitHub Actions workflows
 │       ├── tests.yaml
@@ -346,22 +348,6 @@ Solution:
 1. Check server health via `mcpd` API
 2. Verify tool exists on the server
 3. Check `mcpd` logs for errors
-4. Check `stderr` output from `mcpd-proxy` for detailed error messages
-
-## Logging
-
-`mcpd-proxy` logs to `stderr` (`stdout` is reserved for MCP protocol):
-
-```
-============================================================
-mcpd-proxy v0.0.1
-============================================================
-mcpd daemon: http://localhost:8090
-API key: not set
-============================================================
-[mcpd-proxy] Connected and ready
-[mcpd-proxy] Error listing tools: <error details>
-```
 
 ## Future Enhancements