mcp

This MCP server provides a simple, facade-like implementation of the Model Context Protocol (MCP). It allows you to define and register custom tools that implement the Tool interface and expose them through a standardized MCP API, making it easier for clients to invoke your tools via a consistent protocol. The README demonstrates how to create a minimal server, register an EchoTool, start the server, and test it with MCP clients such as Claude Desktop or other MCP-compatible clients. The server is designed to be extended by adding your own tools and business logic on top of the provided Tool base class and ToolSchema, then wiring them into an MCPServer instance.

To use it, install the package (or the Agentico replacement if you’re following the newer package), create your server entry point, register your tools, and run the server. Tool implementations should extend the Tool class and define a ToolSchema that describes the tool name, description, and input schema. Once registered, clients can call your tools by name and receive structured responses as defined by the MCP protocol.

Prerequisites:

• Node.js (and optionally Yarn)
• A basic TypeScript project setup if building from sources

Installation steps (example using npm/yarn):

1. Initialize your project (if starting from scratch):

yarn init -y

2. Install MCP server package (the README references @la-rebelion/mcp-server; newer usage may point to Agentico's package):

yarn add @la-rebelion/mcp-server

3. If building from source, install development dependencies and set up TypeScript:

yarn add -D typescript @types/node

4. Create your server entry (example uses build/index.js as the start target after compilation):

• Write your server using the MCPServer class and register tools (as shown in the README example).

5. Build (if using TypeScript):

yarn build

6. Run the server:

yarn start

or

node build/index.js

Note: If you follow the newer Agentico package, replace the installation step with the appropriate package name and usage as documented in Agentico’s MCP server package.

Notes and tips:

• The README suggests that this project has moved to Agentico’s npm package (@agentico/mcp-server). If you are starting a new project, prefer the Agentico package to get the latest updates and improvements.
• The example tool (EchoTool) shows how to define a ToolSchema, how to implement the execute method, and how to register the tool with the MCPServer.
• Start with a simple tool to validate the MCP flow, then progressively add more complex tools and business logic.
• When testing with clients, ensure the server is reachable at the address/port expected by the client and that the tool names used by the client match the registered tool names on the server.
• If you encounter issues, verify TypeScript compilation output (build/index.js) and ensure the Node.js version is compatible with your build artifacts.
• Environment variables can be added under the env object in mcp_config for runtime configuration (e.g., API keys, feature flags).
• If you migrate to the Agentico package, update the import paths and tool registration accordingly, since there might be newer APIs or helpers.