band-mcp-server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
ruby-band-mcp-server
An MCP server for the BAND Open API,
written in Ruby on the official mcp gem and served over stdio.
Tools
Tool | What it does |
| Reports that the server is up and whether |
| Lists the bands you have joined, with the |
| Publishes a text post to a band. Members are push-notified only if |
| Fetches one post by |
| Lists a band's recent posts, newest-modified first, paged with an |
| Reports which of |
| Permanently deletes a post by |
| Lists a post's comments, oldest first unless |
| Adds a comment to a post. BAND does not return its key; find it with |
| Permanently deletes a comment by |
A typical flow is list_bands to find the band, create_post to publish, then get_post with the returned
post_key to confirm. create_post is marked as not read-only, so MCP clients such as Claude Desktop can ask before
running it.
To browse what is already in a band, use list_posts. BAND picks the page size (20 posts); when the result's
next_after is not null, pass it back as after to get the next page.
To read the discussion on a post, use list_comments with the post's band_key and post_key. Comments come oldest
first; set newest_first to reverse that. BAND chose a page size of 20 when tested. Pass next_after back as after exactly as
returned: it remembers the order, so a page after the first needs no newest_first.
To join in, use create_comment. BAND confirms the comment without saying what its key is, so call list_comments
afterwards to confirm it landed and to get its comment_key.
To take a post down, use remove_post; it is marked destructive, so clients can ask before running it. Run
check_permissions with contents_deletion first. BAND's docs say that permission does not check authorship, so
removing someone else's post can still fail. remove_comment works the same way on a comment_key from
list_comments, and BAND's docs add that it can only remove comments made through this app.
Related MCP server: Basecamp MCP Server
Requirements
Ruby 4.0 or newer.
Install
gem install band-mcp-serverThis puts a band-mcp-server executable on your PATH. To run it without installing, RubyGems can fetch and run it
on demand (the gem and executable share a name, but gem exec needs the gem named explicitly):
gem exec -g band-mcp-server band-mcp-serverDocker
If you would rather not manage a Ruby 4.0 install, a multi-architecture (amd64 and arm64) image of each release is
published to ghcr.io/ktgeek/band-mcp-server. The server speaks MCP over stdio, so run it with -i, and pass the
token through the environment (the image has no config file):
export BAND_ACCESS_TOKEN=your-token
docker run -i --rm -e BAND_ACCESS_TOKEN ghcr.io/ktgeek/band-mcp-serverTags are the release version (for example 1.0.0) and latest. Register it with Claude Code:
claude mcp add band -e BAND_ACCESS_TOKEN=your-token -- \
docker run -i --rm -e BAND_ACCESS_TOKEN ghcr.io/ktgeek/band-mcp-serverGetting a BAND access token
Register an app on the BAND developer site and get an access token for it; the
API guide covers the details. The server only consumes the token and
sends it to BAND as an Authorization: Bearer header. It does not run any OAuth flow itself.
Configuring the token
Put the token in ~/.config/band-mcp-server/config (or $XDG_CONFIG_HOME/band-mcp-server/config if you set that):
mkdir -p ~/.config/band-mcp-server
echo 'BAND_ACCESS_TOKEN=your-token' > ~/.config/band-mcp-server/config
chmod 600 ~/.config/band-mcp-server/configA value already set in the environment (for example through the MCP client's env setting) takes precedence over
the file.
Running
Register it with Claude Code:
claude mcp add band -- band-mcp-serverThe server speaks MCP over stdio, so it is normally launched by a client rather than run by hand.
Claude Desktop
Claude Desktop starts servers with a minimal environment, so a version manager such as chruby is not active and
the installed executable's #!/usr/bin/env ruby finds the wrong Ruby (the system Ruby, if any). With chruby, launch
the server through chruby-exec, which selects the Ruby and its
GEM_HOME for you.
chruby-exec does that by running the command in a login shell ($SHELL -l -c), so two things must hold. chruby has
to be loaded by a startup file that a non-interactive login shell reads (for zsh, ~/.zprofile or ~/.zshenv, not
only ~/.zshrc). And those startup files must not print anything to stdout: it would land in front of the protocol
stream and Desktop could not parse the handshake.
Find where
chruby-execis installed withwhich chruby-exec. That depends on how you installed chruby, and the path has to be absolute because Desktop'sPATHis minimal.Open Settings → Developer → Edit Config (on macOS this is
~/Library/Application Support/Claude/claude_desktop_config.json) and add abandentry tomcpServers:{ "mcpServers": { "band": { "command": "/path/to/chruby-exec", "args": ["ruby-4", "--", "band-mcp-server"] } } }chruby matches
ruby-4against the installed Rubies by name, so it picks a 4.x Ruby; use a fuller name such asruby-4.0.5to pin one. Rungem install band-mcp-serverunder that same Ruby.Keep the token in the config file described above; it is loaded by absolute path, so the working directory does not matter. Setting
BAND_ACCESS_TOKENin anenvmap instead also works and takes precedence, but puts the secret in Desktop's config file.Without chruby, use the absolute path of the installed executable (
which band-mcp-server) ascommand. If that Ruby is not the firstrubyon Desktop's minimalPATH, use the absolute path of a Ruby 4.0 or newer ascommandinstead, put the executable inargs, and setGEM_HOMEto the directory holding the installed gems (gem env gemdirprints it):{ "mcpServers": { "band": { "command": "/path/to/ruby", "args": ["/path/to/band-mcp-server"], "env": { "GEM_HOME": "/path/to/gem/dir" } } } }With Docker, none of the above applies: Desktop only needs the absolute path of
docker(which docker), and the token goes in anenvmap, which puts the secret in Desktop's config file:{ "mcpServers": { "band": { "command": "/path/to/docker", "args": ["run", "-i", "--rm", "-e", "BAND_ACCESS_TOKEN", "ghcr.io/ktgeek/band-mcp-server"], "env": { "BAND_ACCESS_TOKEN": "your-token" } } } }To keep the secret out of that file, write
BAND_ACCESS_TOKEN=your-tokento a file only you can read, remove theenvmap and the"-e", "BAND_ACCESS_TOKEN"pair, and add"--env-file", "/path/to/that/file"before the image name inargs.Quit Claude Desktop completely (Cmd-Q) and reopen it. The
bandtools appear in the tools menu of a new chat.
Then ask Claude to run ping, which reports whether the token is set without showing it, and try "Which bands am I
in?" to confirm the connection. Desktop asks before it runs a tool unless you have set that tool to always allow.
Keep the prompt on for create_post and create_comment: they publish to every member of the band. Read the band and
the wording in the request before approving. For create_post, members are push-notified only if the request sets
do_push. Keep the prompt on for remove_post and remove_comment too: what they delete is gone for every member and
cannot be restored, so check the keys before approving.
To check the launch command outside Desktop, run it with a bare environment. A JSON initialize response means the
server starts under that Ruby with its gems; it does not check the token, which ping does:
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"0"}}}' |
env -i HOME="$HOME" PATH=/usr/bin:/bin "$(which chruby-exec)" ruby-4 -- band-mcp-serverIf the tools do not show up, read ~/Library/Logs/Claude/mcp-server-band.log:
Symptom in the log or tool result | Cause |
|
|
| No installed Ruby matches the name in |
|
|
| The chosen Ruby is older than 4.0; point |
| No config file with the token, and no |
| chruby is only loaded in |
Desktop cannot parse the server's output | A shell startup file prints to stdout; |
| BAND's "Unauthorized" code: the token is missing, invalid or expired. |
Development
From a checkout, use Bundler instead of the installed gem. A .env in the checkout root takes priority over the
user config file, and bin/band-mcp-server (which sets up Bundler itself) replaces band-mcp-server:
chruby ruby-4.0.5 # or any manager that reads .ruby-version
bundle install
cp .env.example .env # then set BAND_ACCESS_TOKEN
claude mcp add band -- /path/to/ruby-band-mcp-server/bin/band-mcp-serverbundle exec rake # rubocop, rbs drift check, steep, rspec
bundle exec rake -T # every task, including auditlib/ is typed with rbs-inline annotations and checked by
Steep; regenerate sig/generated/ with bundle exec rake rbs:generate after
changing them. See AGENTS.md for conventions and architecture.
main is protected: changes land through a pull request with green CI.
License
GPL-3.0. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Use your Pronto feed, Spaces, Posts, Artifacts, and agents from any MCP client.
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
Discover MCP servers and A2A agents; verify, message, post, follow, react, and receive webhooks.
Related MCP Servers
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage Basecamp 3 projects, todos, messages, card tables, documents, uploads, and search through OAuth-authenticated API calls.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to browse, search, and manage Basecamp 3 projects, todolists, todos, messages, campfires, card tables, inbox forwards, documents, uploads, comments, events, and webhooks through OAuth-authenticated API calls, including downloading attachments as readable content.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage Basecamp 3 projects, todos, messages, card tables, documents, uploads, and search through OAuth-authenticated API calls.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-capable clients to read and manage projects, todos, messages, card tables, documents, uploads, comments, webhooks, and search through OAuth-authenticated Basecamp 3 API calls.-