Skip to main content
Glama
Band MCP Server

Band MCP Server

by kanghouchao

NPM Version Docker Pulls

A fully functional Model Context Protocol (MCP) server that integrates with the Band API. This server enables seamless interaction with the Band social platform through AI assistants and other MCP-compatible tools.

Overview

This server can be used in two primary ways:

  1. As a standalone executable: Installed via npm and configured directly in a compatible MCP client.

  2. As a Docker container: Pulled from Docker Hub and configured in a compatible MCP client to be run on-demand.

Related MCP server: Notion MCP Server

Usage & Client Configuration

To use this server, you need a Band API Access Token. You can obtain one from the Band Developer Portal.

Below are configuration examples for different clients and usage methods.

Example 1: Claude Desktop (NPM version)

This method assumes you have installed the server via npm install -g band-mcp-server.

  1. In Claude Desktop, open Settings > Developer and click Edit Config.

  2. Add the following to the mcpServers object in claude_desktop_config.json:

{
  "mcpServers": {
    "band-api": {
      "command": "band-mcp-server",
      "args": [],
      "env": {
        "BAND_ACCESS_TOKEN": "your_band_api_access_token"
      }
    }
  }
}

Replace your_band_api_access_token with your actual token.

Example 2: Claude Desktop (Docker version)

This method uses the Docker image and does not require npm.

  1. In Claude Desktop, open Settings > Developer and click Edit Config.

  2. Add the following to the mcpServers object in claude_desktop_config.json:

{
  "mcpServers": {
    "band-api-docker": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "BAND_ACCESS_TOKEN=your_band_api_access_token",
        "kanghouchao/band-mcp-server:latest"
      ]
    }
  }
}

Replace your_band_api_access_token with your actual token.

License

This project is licensed under the MIT License.

Available Tools

12 tools
get_albumsB

Get photo albums from a specific band in BAND.

Inputs: band_key (required). Returns: result_code, result_data

get_bandsB

Get the list of bands that the user joined from BAND.

Inputs: no named parameters. Returns: data, success

get_commentsB

Get comments from a specific post in BAND.

Inputs: band_key (required), post_key (required), sort. Returns: result_code, result_data

get_photosB

Get photos from a specific album in BAND.

Inputs: band_key (required), photo_album_key. Returns: result_code, result_data

get_postC

Get a single post from BAND.

Inputs: band_key (required), post_key (required). Returns: result_code, result_data

get_postsB

Get posts from a specific band in BAND.

Inputs: band_key (required), after, limit, locale. Returns: result_code, result_data

get_user_informationB

Get user profile information from BAND. Optionally specify a band_key to get user info within a specific band context.

Inputs: band_key. Returns: data, success

permissionsB

Get post permission information from BAND.

Inputs: band_key (required), permissions (required). Returns: result_code, result_data

remove_commentB

Delete a comment from BAND.

Inputs: band_key (required), comment_key (required), post_key (required). Returns: result_code, result_data

remove_postB

Delete a post from BAND.

Inputs: band_key (required), post_key (required). Returns: result_code, result_data

write_commentB

Write a comment to BAND post.

Inputs: band_key (required), body (required), post_key (required). Returns: result_code, result_data

write_postB

Write a post to BAND.

Inputs: band_key (required), content (required), do_push. Returns: result_code, result_data

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 12 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources and actions in the BAND domain. Tools like get_albums vs get_photos or write_post vs write_comment have no overlap, and the get_* tools are clearly differentiated by what they retrieve.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming. The verbs are clear (get, write, remove) and consistently applied, with no deviations in style or convention across the set.

    Tool Count5/5

    12 tools is well-scoped for a social media/band management domain, covering core operations like reading/writing posts and comments, managing albums and photos, and user/band information. Each tool earns its place without feeling excessive or sparse.

    Completeness4/5

    The tool set provides strong CRUD coverage for posts and comments (get/write/remove), good read access for albums, photos, bands, and user info, and permissions checking. Minor gaps include no update operations for posts/comments and no album/photo creation or deletion tools, but agents can work around these with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers