fix: WASM compilation errors in wasm_typed_tool.rs

[guyernest]

Summary

This PR fixes two compilation errors that prevent pmcp v1.7.0 from building for the wasm32-unknown-unknown target, enabling browser-based MCP clients.

Issues Fixed

1. Missing Clone Trait Bound

Error:

error[E0599]: no method named `clone` found for type parameter `impl Into<String>` in the current scope
   --> src/server/wasm_typed_tool.rs:220:56
    |
220 |         let tool = WasmTypedTool::new_with_schema(name.clone(), schema, handler);
    |                                                        ^^^^^ method not found in `impl Into<String>`

Fix: Added + Clone bound to name parameters in three methods that call name.clone():

• tool_typed (line 200)
• tool_typed_with_schema (line 212)
• tool_typed_simple (line 226)

2. Unresolved Import error_codes

Error:

error[E0432]: unresolved import `crate::server::error_codes`
   --> src/server/wasm_typed_tool.rs:237:24
    |
237 | pub use crate::server::error_codes::{ValidationError, ValidationErrorCode};
    |                        ^^^^^^^^^^^ could not find `error_codes` in `server`

Fix: Added #[cfg(not(target_arch = "wasm32"))] to:

• error_codes re-export (line 237)
• validation module (line 242)
• test_wasm_validation test (line 394)

These items depend on error_codes, which is compiled with #[cfg(not(target_arch = "wasm32"))] in src/server/mod.rs:70.

Changes

File: src/server/wasm_typed_tool.rs

- pub fn tool_typed<T, F>(self, name: impl Into<String>, handler: F) -> Self
+ pub fn tool_typed<T, F>(self, name: impl Into<String> + Clone, handler: F) -> Self

- pub fn tool_typed_with_schema<T, F>(self, name: impl Into<String>, ...) -> Self
+ pub fn tool_typed_with_schema<T, F>(self, name: impl Into<String> + Clone, ...) -> Self

- pub fn tool_typed_simple<T, F>(self, name: impl Into<String>, handler: F) -> Self
+ pub fn tool_typed_simple<T, F>(self, name: impl Into<String> + Clone, handler: F) -> Self

+ #[cfg(not(target_arch = "wasm32"))]
  pub use crate::server::error_codes::{ValidationError, ValidationErrorCode};

+ #[cfg(not(target_arch = "wasm32"))]
  pub mod validation {
      // ... module contents
  }

  #[test]
+ #[cfg(not(target_arch = "wasm32"))]
  fn test_wasm_validation() {
      // ... test contents
  }

Testing

✅ Library builds successfully:

cargo check --lib --all-features
# Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.59s

✅ All library tests pass:

cargo test --lib --all-features
# test result: ok. 418 passed; 0 failed; 0 ignored; 0 measured

✅ No clippy warnings:

cargo clippy --lib --all-features -- -D warnings
# Finished `dev` profile [unoptimized + debuginfo] target(s) in 4.59s

✅ Formatting check passes:

cargo fmt --all -- --check
# (no output = success)

Use Case

This fix enables browser-based MCP management UIs that:

• Test MCP servers interactively from the browser
• Execute YAML test scenarios client-side
• Provide zero-backend-cost testing for MCP servers
• Demonstrate MCP capabilities in presentations

Impact

• Before: pmcp v1.7.0 fails to compile for wasm32-unknown-unknown
• After: pmcp v1.7.0 compiles successfully for WASM targets
• Breaking Changes: None - this is a bug fix
• API Changes: Only adds + Clone bound to existing impl Into<String> parameters (satisfied by all common types like &str, String)

Related Issues

This addresses the WASM compilation regression introduced in v1.7.0. Users were forced to downgrade to v1.2.2 to build WASM clients.

---

🤖 Generated with Claude Code

Co-Authored-By: Claude noreply@anthropic.com