Beeper Texts MCP Server
A local-only MCP (Model Context Protocol) server tested on macOS that exposes Beeper Texts data (messages, contacts, chats) for use with AI assistants and automation tools. Local-only means the MCP accesses your local Beeper SQLite database only, and does not make or trigger any network requests.
Features
- Chat Management: List and browse conversations across platforms
- Message Access: Retrieve messages from specific chats
- Search: Search messages by content, chat name, or by sender
- Media Access: Fetch attachment bytes/paths via a URI returned in messages
- Multi-Platform Support: Tested with WhatsApp, Telegram, Signal, Instagram, Twitter/X and LinkedIn. Should work with any Beeper-supported platform.
Requirements
- macOS only: This server relies on Beeper Desktop's local database structure only
- Beeper Desktop: Must be installed, configured with at least one connected account and running to receive new messages
- Python 3.10+: Required for running the server
Installation
Install from PyPI using pip or uvx:
pip install mcp-beeper-texts
Or use uvx for isolated execution:
uvx mcp-beeper-texts
Configuration
Claude Desktop
Add the following to your Claude Desktop configuration file (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"beeper": {
"command": "uvx",
"args": ["mcp-beeper-texts"]
}
}
}
Other MCP Clients
For other MCP clients, use the command:
uvx mcp-beeper-texts
The server communicates over stdio transport.
TODO
Add support for:
- Creating, Editing, and Deleting drafts
- Sending messages
- Sending media attachments
Available Tools
list_chats
List group and DM chats with metadata.
label(optional): Filter set:inbox,archive,favourite,all,unread(default:inbox)sort_by(optional):latest_message,last_active, orname(default:latest_message)limit(optional): Max chats to return (default: 25)recent_messages_limit(optional): Include last N messages per chat (default: 3, set 0 to disable)max_participants(optional): Max participant names for groups (default: 5)include_low_priority(optional): Include low priority in non-inbox views (default: false)
get_messages
Get chronologically ordered messages from a specific chat.
chat_id(required)limit(optional): Default 50before/after(optional): ISO-8601 timestamps to page
search_message_contents
Search message contents across chats with optional context.
query(required)chat_id(optional): Limit to one chatlimit(optional): Default 25include_context(optional): Include surrounding messages (default: true)
search_chat_names
Search chats by name/title with label filtering.
query(required)label(optional): Defaultalllimit(optional): Default 25
get_person_messages
Get messages sent by a specific person across chats.
person_name(required)limit(optional): Max per chat (default: 50)platform(optional): Platform filterchat_type(optional):dm,group, oralldays_back(optional): Only include messages from the last N daysinclude_context(optional): Include surrounding messages
get_media_attachment
Retrieve media attachment bytes/path by URI returned in Message.attachments.
attachment_uri(required): e.g.,beeper://attachment/{message_id}/{attachment_index}optimize_for_context(optional): For images, resize to ≤1568px for efficiency (default: true)
Development
Setup
- Clone the repository
- Install dependencies:
uv sync - Run tests:
uv run pytest - Format code:
uv run ruff format . - Lint code:
uv run ruff check . --fix
Testing
Run the test suite:
uv run pytest tests/ -v
MCP Inspector
Use the MCP Inspector for development and testing:
uv run mcp dev src/mcp_beeper_texts/server.py
Claude Desktop
For Claude Desktop testing (or other local MCP clients), use this configuration in ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"Beeper": {
"command": "/opt/homebrew/bin/uv",
"args": [
"run",
"--dev",
"--project",
"/path/to/your/mcp-beeper-texts",
"mcp-beeper-texts"
]
}
}
}
Replace /path/to/your/mcp-beeper-texts with the actual path to your local repository.
Hot-Reload Development
For faster development with automatic reloading when files change, you can use MCP Reloader:
# Install MCP Reloader (one-time setup)
git clone https://github.com/mizchi/mcp-reloader.git
cd mcp-reloader
npm install
npm run build
# Run with hot-reload (from your project directory)
npx mcp-reloader --command "uv run src/mcp_beeper_texts/server.py"
This automatically restarts the server when you modify any Python files, providing a faster development workflow.
Database Access
The server reads from Beeper's local SQLite databases located at:
~/Library/Application Support/BeeperTexts/
index.db: Beeper UI-optimized message and chat index and metadatalocal-{platform}/megabridge.db: Platform-specific data and contacts
The server only requires read access for most operations, with write access eventually needed for draft management and message sending.
Troubleshooting
"Beeper directory not found"
Ensure Beeper Desktop is installed and has been run at least once. The application creates its data directory on first launch.
"Database not found"
Make sure Beeper Desktop is properly configured with at least one connected account. The databases are created when platforms are connected.
Permission errors
Ensure the server has read access to ~/Library/Application Support/BeeperTexts/. This should be automatic on macOS.
License
MIT License - see LICENSE file for details.
Contributing
Contributions are welcome. Please follow these steps:
- Fork the repository
- Create a feature branch (
git checkout -b feat/new-feature) - Add functionality and tests if applicable
- Run the test suite (
uv run pytest) - Format and lint your code (
uv run ruff format . && uv run ruff check . --fix) - Commit, Push, and create a Pull Request
Changelog
0.0.1
- Initial release
- Basic chat, message, and contact management
- Search functionality across all platforms
- Basic test suite
Metadata
Release files for mcp-beeper-texts 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_beeper_texts-0.0.2.tar.gz | 16.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_beeper_texts-0.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.2 kB
Release files / mcp_beeper_texts-0.0.2.tar.gz
| Download URL | mcp_beeper_texts-0.0.2.tar.gz |
|---|---|
| Size | 16.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b64b703fa8e9f92a4589ef4c01186cfb21ee2cfb7e626f922bc7fcb82bb598d1
|
|
BLAKE2b-256 checksum How to use checksums |
1274beb4bedbaac665e44331d08b5a78bbc952be520e7194c53a6daef6d7cf45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 11, 2025.
Transparency logRelease files / mcp_beeper_texts-0.0.2-py3-none-any.whl
| Download URL | mcp_beeper_texts-0.0.2-py3-none-any.whl |
|---|---|
| Size | 18.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71b09cdf74167e3d1e2875824763106da98856dd7cc67e3db192b41a3c5e833d
|
|
BLAKE2b-256 checksum How to use checksums |
1fce0990a1261ca9535780bfdc6282509c6bf11df27b22c6c1c8bbf6f88f01cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 11, 2025.
Transparency logSecurity for mcp-beeper-texts 0.0.2
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mcp_beeper_texts-0.0.2.tar.gz
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 11, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.