Skip to main content
Glama
wirebox-sh

@wirebox-sh/mcp

by wirebox-sh

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WIREBOX_API_KEYYesYour Wirebox secret API key (starts with wb_live_ or wb_test_). Get one at wirebox.sh/console.
WIREBOX_BASE_URLNoOverride the API base URL (defaults to https://api.wirebox.sh).https://api.wirebox.sh
WIREBOX_IDENTITYNoDefault agent handle (e.g. alice) to scope communication actions.

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
wirebox_whoamiA

Show this agent's Wirebox identity (handle, email address, display name) and iMessage router connection status.

wirebox_imessage_sendA

Send an iMessage. Reply into an existing conversation via conversationId, or start a message to a recipient E.164 phone number / Apple ID email.

wirebox_imessage_list_conversationsA

List active iMessage conversations for this agent, including participants, last message timestamp, and unread count.

wirebox_imessage_get_messagesA

Fetch message history for a specific iMessage conversation.

wirebox_mail_sendA

Send an email message from this agent's Wirebox mailbox.

wirebox_mail_listB

List email messages in this agent's mailbox.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct action: sending vs listing emails, sending iMessages, listing conversations, fetching message history, and getting identity/status. There is no overlap between tools that could cause an agent to select the wrong one.

Naming Consistency4/5

All tools follow a consistent wirebox_{channel}_{action} pattern with snake_case. Minor inconsistency exists: mail_list doesn't specify what is listed (messages), while imessage uses list_conversations and get_messages, but the pattern is still predictable.

Tool Count5/5

Six tools is well-scoped for a messaging server covering two channels (email and iMessage) plus identity/status. Each tool has a clear purpose and none are redundant.

Completeness4/5

Core messaging workflows are supported: send and list email, send iMessage, list conversations, and fetch messages. Minor gaps exist such as no single-email fetch, no email reply, or no mark-as-read, but agents can accomplish primary tasks.

Maintenance

ActivityMaintained
ResponsivenessNo issues