groupme-mcp
A Model Context Protocol (MCP) server that wraps the GroupMe API v3, letting AI assistants read and send GroupMe messages, manage groups, interact with bots, and more.
Tools
| Category | Tools |
|---|---|
| Groups | list_groups, list_former_groups, get_group, create_group, update_group, destroy_group, join_group, rejoin_group |
| Members | add_members, get_member_results, remove_member, update_membership |
| Messages | list_messages, send_message |
| Direct Messages | list_direct_messages, send_direct_message |
| Chats | list_chats |
| Likes | like_message, unlike_message |
| Bots | create_bot, post_as_bot, list_bots, destroy_bot |
| Users | get_me, update_user |
| Blocks | list_blocks, check_block, create_block, delete_block |
Skill
Install the companion skill to give Claude built-in knowledge of GroupMe workflows — group name resolution, message pagination, the async add_members flow, and more — without needing to prompt it each time.
The skill folder lives at skill/groupme-mcp/.
Install in Claude.ai: Settings → Capabilities → Skills → Upload skill → select the skill/groupme-mcp/ folder (zipped).
Install in Claude Code: place the skill/groupme-mcp/ folder in your Claude Code skills directory.
Requirements
- Python 3.12+
- A GroupMe access token — get one at dev.groupme.com or use the OAuth helper
Usage
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"groupme": {
"command": "uvx",
"args": ["groupme-mcp"],
"env": {
"GROUPME_TOKEN": "<your-token>"
}
}
}
}
Local development
git clone https://github.com/KalebJS/groupme-mcp
cd groupme-mcp
export GROUPME_TOKEN=<your-token>
uv run mcp dev main.py # opens MCP Inspector in browser
Getting a Token
oauth/get_token.py runs a local OAuth flow using only the Python stdlib — no extra dependencies.
- Create an application at dev.groupme.com/applications.
- Set the callback URL to
http://localhost:8080/callback. - Run the helper:
python oauth/get_token.py --client-id YOUR_CLIENT_ID
The script opens your browser, waits for the GroupMe redirect, and prints the token along with the export command to set it.
Development
# Install dev dependencies
uv sync --group dev
# Install pre-commit hooks
uv run --group dev pre-commit install
# Run tests
uv run --group dev pytest tests/ -v
# Lint
uv run --group dev pre-commit run --all-files
License
MIT
Metadata
Release files for groupme-mcp 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| groupme_mcp-1.0.1.tar.gz | 72.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| groupme_mcp-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 80.4 kB
Release files / groupme_mcp-1.0.1.tar.gz
| Download URL | groupme_mcp-1.0.1.tar.gz |
|---|---|
| Size | 72.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
576096e2e9fbe8be8219bdfc2e1e916947a3e4209b5df5aabb66a68a4b4e4c96
|
|
BLAKE2b-256 checksum How to use checksums |
54f55827bdfafbd1160b13cbb4c030e4bafcf585f704d472eb84d3412dd86b66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency logRelease files / groupme_mcp-1.0.1-py3-none-any.whl
| Download URL | groupme_mcp-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
26e12554708f17a0663e90ca81c1c14b8f999641654a3450acf2d3ce31174e90
|
|
BLAKE2b-256 checksum How to use checksums |
4cca424bb479f1ce7acff91f651d58c7997c8e33968c59d2f92d5c9c8475b361
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 26, 2026.
Transparency log