Skip to content
Back to search

mcp-client-server

An MCP Server that's also an MCP Client. Useful for letting Claude develop and test MCPs without needing to reset the application.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/willccbb--mcp-client-server/badge.svg)](/listings/willccbb--mcp-client-server)

HTML

<a href="/listings/willccbb--mcp-client-server"><img src="/api/listings/willccbb--mcp-client-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# Install dependencies
npm install

# Build the TypeScript project
npm run build

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 138 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # MCP Test Client
  2. An MCP middleware that acts as both a server (to Claude) and a client (to servers under test) for testing MCP servers during development.
  3. ## Architecture
  4. The MCP Test Client has a dual role:
  5. - It's a **server** registered with Claude that exposes tools for testing
  6. - It's a **client** that connects to and tests other MCP servers
  7. ```
  8. ┌─────────────┐ ┌───────────────────┐ ┌────────────────┐
  9. │ │ Tools │ │ Client │ │
  10. │ Claude │─────────>│ MCP Test Client │─────────>│ Server Under │
  11. │ │ │ │ │ Test │
  12. └─────────────┘ └───────────────────┘ └────────────────┘
  13. ```
  14. This architecture lets you test MCP servers without registering them directly with Claude.
  15. ## Features
  16. - Deploy MCP servers to test environments
  17. - Call individual tools with custom arguments
  18. - Run automated test suites
  19. - View server logs
  20. - Test servers before formal registration with Claude
  21. ## Implementation
  22. The MCP Test Client is implemented with:
  23. - **Process Management**: Spawns and manages MCP server processes
  24. - **MCP SDK Client**: Uses the official MCP SDK to communicate with servers
  25. - **Custom Transport**: Implements a custom transport for stdio communication
  26. - **Test Execution**: Runs tests and validates responses
  27. - **CLI Interface**: Provides an interactive testing interface
  28. The current implementation is Phase 1 of the design plan, with future enhancements planned for Phases 2 and 3.
  29. ## Installation
  30. ```bash
  31. # Install dependencies
  32. npm install
  33. # Build the TypeScript project
  34. npm run build
  35. ```
  36. ## Usage
  37. ### As an MCP Server
  38. The MCP Test Client is registered with Claude via the `claude-mcp-local` script. You can use the following tools:
  39. 1. Deploy a server:
  40. ```typescript
  41. mcp__mcp-test__mcp_test_deploy_server({
  42. name: "my-server",
  43. source_path: "/path/to/server",
  44. env_vars: {
  45. "API_KEY": "${API_KEY}"
  46. }
  47. })
  48. ```
  49. 2. Call a tool on a deployed server:
  50. ```typescript
  51. mcp__mcp-test__mcp_test_call_tool({
  52. server_name: "my-server",
  53. tool_name: "tool_name",
  54. arguments: {
  55. // Tool-specific arguments
  56. }
  57. })
  58. ```
  59. 3. Run tests against a server:
  60. ```typescript
  61. mcp__mcp-test__mcp_test_run_tests({
  62. server_name: "my-server"
  63. })
  64. ```
  65. 4. View server logs:
  66. ```typescript
  67. mcp__mcp-test__mcp_test_get_logs({
  68. server_name: "my-server",
  69. lines: 100
  70. })
  71. ```
  72. 5. List deployed servers:
  73. ```typescript
  74. mcp__mcp-test__mcp_test_list_servers({})
  75. ```
  76. 6. Stop a server:
  77. ```typescript
  78. mcp__mcp-test__mcp_test_stop_server({
  79. server_name: "my-server"
  80. })
  81. ```
  82. ### As a CLI Tool
  83. Run the CLI interface for testing:
  84. ```bash
  85. # Use npm script
  86. npm run test
  87. # Or run directly
  88. node dist/test-runner.js
  89. ```
  90. This provides an interactive menu for deploying, testing, and managing MCP servers.
  91. ## Development Workflow
  92. The MCP Test Client supports this workflow:
  93. 1. Develop an MCP server in the playground directory
  94. 2. Deploy it to the test environment with MCP Test Client
  95. 3. Test functionality, call individual tools, and debug issues
  96. 4. Fix and iterate until the server works correctly
  97. 5. Migrate the server to mcp-servers/ when ready
  98. 6. Register with Claude through claude-mcp-local
  99. ## Future Enhancements
  100. Planned enhancements include:
  101. - **Phase 2**: Docker-based container management, comprehensive test suites
  102. - **Phase 3**: Migration tools, more advanced test validation
  103. See `notes/mcp_test_client_design.md` for the complete design document.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.