MCP.so
Sign In

Dummy MCP Server

@AngeloBoggio

Basic information

Category

Other

Transports

stdio

Author

AngeloBoggio

About Dummy MCP Server

Creating an MCP server in order to plug it with a slack-bot

#dummy-mcp-server#slack-bot#typescript

Dummy MCP Server config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Dummy MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Dummy MCP Server?

Dummy MCP Server is a basic Master Control Program server written in TypeScript that provides a framework for handling MCP commands and can be integrated with a Slack bot. It is intended for developers who need a starting point for building MCP command processing with Express.js and Winston logging.

How to use Dummy MCP Server?

Install dependencies with npm install, create a .env file with PORT, SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, SLACK_APP_TOKEN, and LOG_LEVEL, then start the development server using npm run dev. The server listens on port 3000 by default and exposes GET /health and POST /mcp/command endpoints.

Key features of Dummy MCP Server

  • Express.js server with TypeScript support
  • Winston logging setup
  • Environment-based configuration via .env
  • Ready for Slack bot integration
  • Health check endpoint at GET /health
  • Error handling middleware

Use cases of Dummy MCP Server

  • Prototyping a simple MCP command handler before adding full Slack integration
  • Learning how to structure an MCP server with TypeScript and Express
  • Running a lightweight health-checkable service for development environments

Frequently asked questions

1

What does Dummy MCP Server do?

It is a placeholder server that receives MCP commands via `POST /mcp/command` and provides a health check endpoint. It is designed to be extended for Slack bot integration.

2

How do I start the server?

Run `npm run dev` for development with hot reload, or first run `npm run build` then `npm start` for production.

3

What dependencies does it require?

Node.js and npm. The server uses Express, TypeScript, and Winston (as inferred from `package.json` usage). Slack bot tokens are expected in the `.env` file.

4

Where does log data live?

Logs are written to a `logs/` directory (configured by Winston). The exact file name is not specified.

5

Is authentication available?

The current version does not implement authentication or authorization; the `POST /mcp/command` endpoint is unprotected. Future enhancements include authentication.

Comments

More Other MCP servers