Skip to main content
Glama
tetmin

Beeper Texts MCP Server

by tetmin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_chatsA

List group and DM chats with metadata, filtering and sorting options.

Args:
    label: chat label/folder - "inbox", "archive", "all","favourite", "unread" (default "inbox")
    sort_by: Sort order - "latest_message", "last_active" or "name" (default "latest_message")
    limit: Maximum number of chats to return (default 25)
    recent_messages_limit: Number of recent messages to include per chat (default 3, set to 0 to disable)
    max_participants: Maximum number of participant names to list for group chats (default 5)
    include_low_priority: Whether to include low priority chats in archive/all views (default False)

Returns:
    List of Chat objects with metadata including platform, truncated recent
    messages for context, participants, timestamps etc.
get_messagesA

Get chronologically orderedmessages from a specific chat with metadata and optional filtering.

Args:
    chat_id: ID of the chat/conversation
    limit: Maximum number of messages to return (default 50)
    before: Optional ISO-8601 timestamp to get messages before this date
    after: Optional ISO-8601 timestamp to get messages after this date

Returns:
    List of Message objects with metadata including platform, sender names, timestamps, reactions etc.
search_message_contentsA

Search message contents across all chats with optional context and filtering.

Args:
    query: Text to search for across message contents
    chat_id: Optional chat ID to limit search to specific chat
    limit: Maximum number of results to return (default 25)
    include_context: Whether to include messages before and after matches (default True)

Returns:
    List of ChatSearchResult objects with message, chat info, and context
search_chat_namesA

Search for chats by name/title with filtering by label.

Args:
    query: Chat name or partial name to search for
    label: Filter results by chat type: 'inbox', 'archive', 'favourite', 'all' (default 'all')
    limit: Maximum number of results to return (default 25)

Returns:
    List of Chat objects matching the search criteria
get_person_messagesA

Get all messages sent by a specific person across all chats.

Args:
    person_name: Name of the person to search for
    limit: Maximum number of messages per chat (default 50)
    platform: Filter by platform ("WhatsApp", "Telegram", etc.)
    chat_type: Filter by chat type ("dm", "group", or "all")
    days_back: Only include messages from the last N days
    include_context: Include surrounding messages for context

Returns:
    List of ChatSearchResult objects, each containing a chat and the person's messages in that chat
get_media_attachmentA

Retrieve media attachment content by URI from message attachments.

Args:
    attachment_uri: URI from Message.attachments (e.g., "beeper://attachment/{message_id}/{attachment_index}")
    optimize_for_context: For images, resize to ≤1568px max dimension for cost efficiency (default True)

Returns:
    For images: {"type": "image", "mime_type": "image/jpeg", "base64": "..."}
    For audio: {"type": "audio", "mime_type": "audio/mpeg", "base64": "..."}
    For files/videos: {"type": "file"|"video", "mime_type": "...", "filepath": "/path/to/file"}
    For errors: {"error": "description", "uri": "original_uri"}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Tools are mostly distinct with clear purposes. Some overlap exists between search_message_contents and get_person_messages (both return messages), but their descriptions clarify different use cases (text query vs person name). Similarly, list_chats and search_chat_names have overlapping functionality but are distinguished by filtering vs name search.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_message_contents, list_chats, get_messages). The verbs are appropriately varied (search, list, get) and predictably used across the set.

Tool Count5/5

Six tools is well-scoped for a messaging server. Each tool fulfills a clear role: searching messages, listing chats, retrieving messages, searching chats, getting person messages, and fetching media attachments. No tool feels redundant or missing.

Completeness2/5

The tool set is entirely read-only, lacking any write operations like sending messages, creating chats, or muting conversations. This is a significant gap for a messaging server, as agents cannot perform basic actions beyond retrieval.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources