mcp-server-routine-bot

PassionZale/mcp-server-routine-bot

3.1

If you are the rightful owner of mcp-server-routine-bot and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

The Model Context Protocol (MCP) Server is a specialized server designed to handle and manage model context protocols, facilitating seamless communication and data exchange between different systems and applications.

MCP Server Routine Bot

Version License Downloads Status

A Model Context Protocol (MCP) server designed to automate routine operations and enhance productivity through intelligent task automation.

⚠️ Note: This project is currently under active development. Features may change, and some functionality may be incomplete or unstable.

Overview

MCP-Server-Routine-Bot is an intelligent automation assistant that streamlines repetitive workflows and eliminates time-consuming manual tasks. Built on the Model Context Protocol (MCP) framework, it seamlessly integrates with popular development tools to provide automated solutions for common operational challenges.

Key Features

  • Task Automation: Automatically handle repetitive daily operations
  • Tool Integration: Native support for Jenkins and TAPD platforms
  • Smart Workflows: Customizable automation pipelines for various scenarios
  • Real-time Monitoring: Track and manage automated processes
  • Hot Reload: Development-friendly architecture with HRM support

Quick Start

Configuration

Configure the server with your platform credentials:

{
  "mcpServers": {
    "mcp-server-routine-bot": {
      "command": "npx",
      "args": ["-y", "@code-sugar/mcp-server-routine-bot@latest"],
      "env": {
        "TAPD_NICK": "your_tapd_nickname",
        "TAPD_GROUP_NICKS": "nickname|nickname|nickname",
        "TAPD_DEFAULT_WORKSPACE_ID": "your_tapd_default_workspace_id",
        "TAPD_BASE_URL": "https://api.tapd.cn",
        "TAPD_ACCESS_TOKEN": "your_tapd_access_token",
        "JENKINS_BASE_URL": "your_jenkins_base_url",
        "JENKINS_USERNAME": "your_jenkins_username",
        "JENKINS_ACCESS_TOKEN": "your_jenkins_access_token",
        "GITLAB_BASE_URL": "your_gitlab_base_url",
        "GITLAB_ACCESS_TOKEN": "your_gitlab_access_token"
      }
    }
  }
}

Environment Variables

VariableRequiredDefaultDescription
TAPD_NICK-Your TAPD account nickname
TAPD_GROUP_NICKS-Your TAPD group nicknames
TAPD_DEFAULT_WORKSPACE_ID-Your TAPD default workspace_id
TAPD_BASE_URLhttps://api.tapd.cnTAPD API base URL
TAPD_ACCESS_TOKEN-TAPD API access token
JENKINS_BASE_URL-Jenkins server base URL
JENKINS_USERNAME-Jenkins username
JENKINS_ACCESS_TOKEN-Jenkins API access token
GITLAB_BASE_URL-Gitlab API base URL
GITLAB_ACCESS_TOKEN-Gitlab API access token

Development Guide

Prerequisites

  • Node.js >= 18
  • npm or yarn

Setup

  1. Clone the repository:

    git clone https://github.com/PassionZale/mcp-server-routine-bot.git
    cd mcp-server-routine-bot
    
  2. Install dependencies:

    npm install
    
  3. Create environment configuration:

    cp .env.example .env
    # Edit .env with your credentials
    

Development Modes

Option 1: MCP Inspector (No HRM)

For debugging and inspection:

  1. Start development server:

    npm run inspector
    
  2. Configure your MCP client:

    {
      "mcpServers": {
        "local-mcp-server-routine-bot": {
          "command": "node",
          "args": ["/path/to/your/mcp-server-routine-bot/dist/index.js"],
          "env": {
            "TAPD_NICK": "your_tapd_nickname",
            "TAPD_GROUP_NICKS": "nickname|nickname|nickname",
            "TAPD_DEFAULT_WORKSPACE_ID": "your_tapd_default_workspace_id",
            "TAPD_BASE_URL": "https://api.tapd.cn",
            "TAPD_ACCESS_TOKEN": "your_tapd_access_token",
            "JENKINS_BASE_URL": "your_jenkins_base_url",
            "JENKINS_USERNAME": "your_jenkins_username",
            "JENKINS_ACCESS_TOKEN": "your_jenkins_access_token",
            "GITLAB_BASE_URL": "your_gitlab_base_url",
            "GITLAB_ACCESS_TOKEN": "your_gitlab_access_token"
          }
        }
      }
    }
    

Note:

  • The inspector command automatically reads environment variables from the .env file
  • Changes to src/index.ts and src/server.ts require manual server restart
  • Changes to other files require re-running the inspector command
Option 2: Reloaderoo (With HRM)

For development with Hot Reload support:

  1. Install reloaderoo globally:

    npm install -g reloaderoo
    
  2. Start development server:

    npm run build:watch
    
  3. Configure your MCP client:

    {
      "mcpServers": {
        "dev-mcp-server-routine-bot": {
          "command": "reloaderoo",
          "args": [
            "proxy",
            "log-level",
            "debug",
            "--",
            "node",
            "/path/to/your/mcp-server-routine-bot/dist/index.js"
          ],
          "env": {
            "TAPD_NICK": "your_tapd_nickname",
            "TAPD_GROUP_NICKS": "nickname|nickname|nickname",
            "TAPD_DEFAULT_WORKSPACE_ID": "your_tapd_default_workspace_id",
            "TAPD_BASE_URL": "https://api.tapd.cn",
            "TAPD_ACCESS_TOKEN": "your_tapd_access_token",
            "JENKINS_BASE_URL": "your_jenkins_base_url",
            "JENKINS_USERNAME": "your_jenkins_username",
            "JENKINS_ACCESS_TOKEN": "your_jenkins_access_token",
            "GITLAB_BASE_URL": "your_gitlab_base_url",
            "GITLAB_ACCESS_TOKEN": "your_gitlab_access_token"
          }
        }
      }
    }
    

Building for Production

npm run build

The compiled output will be available in the dist/ directory.

Troubleshooting

Common Issues

  1. Server not responding: Ensure all required environment variables are set
  2. Authentication errors: Verify your access tokens are valid and have proper permissions
  3. Connection timeouts: Check network connectivity to your configured services

Debugging

Enable debug logging by setting the log level:

# When using reloaderoo
reloaderoo proxy log-level debug -- node dist/index.js

Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Commit your changes (git commit -m 'Add some AmazingFeature')
  4. Push to the branch (git push origin feature/AmazingFeature)
  5. Open a Pull Request

License

This project is licensed under the MIT License - see the file for details.

Author

Lei Zhang - @PassionZale

Project Link: https://github.com/PassionZale/mcp-server-routine-bot