mcp

This MCP server implements the Model Context Protocol (MCP) to provide a simplified API for interacting with tools via a server that you can extend with your own Tool implementations. It ships with a facade pattern that lets you register custom tools and expose them through the MCP API, making it easier for clients to discover and execute those tools. The README example shows how to implement a basic EchoTool as a demonstration: you create a Tool subclass, define its schema, and register it with the MCPServer. After building and starting the server, clients can invoke registered tools by name and pass the required input according to each tool's schema. The server architecture is designed to be extended by adding more tools in separate files and registering them at startup.

Prerequisites:

• Node.js and npm/yarn installed
• TypeScript and build setup if you plan to develop tools

Step-by-step installation:

1. Clone the repository or create your project that will host the MCP server.
2. Install dependencies (adjust to your package manager):
   • npm install or yarn install
3. If you are starting from the example in the README, add the MCP server package to your project:
   • yarn add @agentico/mcp-server
4. Create your server entry (for example build/index.js after compiling TypeScript) and implement/register your tools as shown in the README example.
5. Build the project (if using TypeScript):
   • yarn build
6. Run the server:
   • yarn start
   • or node build/index.js

Notes:

• Ensure your TypeScript transpilation outputs to build/index.js (or adjust the mcp_config path accordingly).
• You can test with MCP clients that support MCP once the server is running.

Tips and common considerations:

• If you add more tools, keep their schemas clear and well-documented so clients can construct correct inputs.
• The server is designed to be extended with your own tools under the tools/ directory or similar structure; follow the EchoTool example to implement custom behavior.
• When deploying, verify the runtime environment (Node version, package externals) matches your build outputs.
• If you encounter port or binding issues, consider configuring environment variables for the server (e.g., PORT) in your deployment setup, even though the README example does not explicitly define them.
• For debugging, run in development mode with console logs and catch blocks as demonstrated in the example main function.