node-typer

node-typer-MCP is a comprehensive Model Context Protocol server that hosts a suite of 20 specialized tools and cognitive components designed to operate autonomously, plan tasks, and orchestrate multiple tools for complex workflows. The server exposes an MCP-compatible interface that allows clients to request tool execution, data transformations, web intelligence, memory persistence, and autonomous task handling. Key capabilities include multi-tool orchestration, autonomous task planning, self-improvement for tool creation, and secure sandboxed execution with audit logging. To interact with it, run the server and use the provided tool syntax examples to invoke specific tools (e.g., typewrite for human-like text simulation, transform_data for data conversions, cognitive_task for autonomous research workflows, or orchestrator_brain for multi-tool workflows). The server can be integrated with Windsurf MCP Manager, Claude Desktop MCP, and n8n AI Workflow Nodes for enterprise automation and AI-assisted workflows.

Prerequisites:

• Node.js v14+ installed on your system
• Git installed

Install and build:

1. Clone the repository git clone https://github.com/ObisDevs/node-typer-MCP.git
2. Navigate to the project directory cd node-typer-MCP
3. Install dependencies npm install
4. Build the project (if applicable) npm run build
5. Start the MCP server (examples below)

Notes:

• The repository uses TypeScript and outputs a dist/server.js for runtime. If your setup uses a different build path, adjust the command accordingly.

Environment variables and configuration:

• PORT: Override the listening port (default is typically 3000).
• DEBUG: Enable or disable verbose logging (true/false).
• STRIPE_SECRET_KEY: If you enable Stripe-based payment processing, configure the API key here.

Common issues:

• Ensure the dist/server.js path matches your build output. Update the mcp_config accordingly.
• If using Docker or another runtime, convert the command to the respective runtime format.
• When integrating with Windsurf or Claude Desktop MCP, ensure the cwd and paths are correctly mounted and accessible.

Configuration tips:

• Use the provided mcp_config snippet as a starting point and adjust the cwd/path to your deployment environment.
• For production, consider setting PORT and DEBUG to appropriate values and securing the STRIPE_SECRET_KEY.