Band MCP Server
The Band MCP Server provides a comprehensive Model Context Protocol interface for the Band social platform, enabling AI assistants and MCP-compatible tools to interact with Band data through full read/write operations.
Core Capabilities:
User & Band Management: Get user profiles, list bands, and verify permissions within specific bands
Post Management: Retrieve, create, and delete posts with pagination and detailed information access
Comment Management: Fetch, add, and remove comments with appropriate permission checks
Media Access: Browse photo albums and photos within Band groups
Secure Authentication: Band API access token integration with comprehensive error handling
Robust Integration: Input validation using Zod schemas, API rate limit handling, and MCP resource/tool exposure
Flexible Deployment: Docker container, npm install, npx execution, or local development options
Enables packaging and deploying the MCP server as a Docker container for simplified deployment and portability.
Handles environment variables for configuring sensitive information like API credentials.
Enables version control and cloning of the repository for installation.
Provides the runtime environment for the MCP server, requiring Node.js 18+ for operation.
Manages dependencies and provides scripts for building, testing, and running the server.
Implements the server using TypeScript for type safety and maintainability.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Band MCP Server show me the latest posts from my band group"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
As a standalone executable: Installed via
npmand configured directly in a compatible MCP client.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.
In Claude Desktop, open Settings > Developer and click Edit Config.
Add the following to the
mcpServersobject inclaude_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.
In Claude Desktop, open Settings > Developer and click Edit Config.
Add the following to the
mcpServersobject inclaude_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 toolsget_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
Scored across 12 tools
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.
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.
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.
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
Related MCP Connectors
Model Context Protocol server for Studex tools, notifications, and profile integrations
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
BGG MCP provides access to the BoardGameGeek API through the Model Context Protocol, enabling retr…
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.575MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides a standardized interface for AI models to access, query, and modify content in Notion workspaces.4MIT
- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.12MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables real-time communication using Server-Sent Events (SSE), providing standardized model management and resource templating capabilities.-