PrivacyFlow MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVACYFLOW_API_KEY | Yes | Your PrivacyFlow API key | |
| PRIVACYFLOW_BASE_URL | No | API base URL | https://api.privacyflow.app |
| PRIVACYFLOW_API_KEY_HEADER | No | Auth header: authorization or x-api-key | authorization |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| privacyflow_check_healthA | Check the health of the PrivacyFlow API. Returns status and version information. No authentication required. |
| privacyflow_verify_api_keyA | Verify that the configured PrivacyFlow API key is valid and return the list of authorized app IDs. No side effects. |
| privacyflow_list_appsA | List all PrivacyFlow apps authorized by your API key. Each app includes its appId, name, active state, and configured messengers (with groupId and provisioning status). Use this to discover which appIds you can pass to privacyflow_send_messages and which messengers each app supports. No input required. |
| privacyflow_poll_messagesA | Poll incoming messages from your PrivacyFlow app queues. Returns messages from all apps authorized by your API key. Messages are consumed on poll (destructive read). Supports Signal, SimpleX, and Session messengers. |
| privacyflow_send_messagesA | Send one or more messages through PrivacyFlow. Accepts an array of message objects. Each message requires appId, contactId, message, and messenger (signal/simplex/session). Optionally include groupId for group replies. Maximum 50 messages per call, 10,000 characters per message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| privacyflow_reply_to_message | Reply to a polled PrivacyFlow message by preserving routing fields |
| privacyflow_broadcast | Broadcast a message to multiple contacts via PrivacyFlow |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| privacyflow-api-docs | PrivacyFlow public API endpoint reference |
| privacyflow-contact-formats | Contact ID formats for Signal, Session, and SimpleX |
TDQS
Scored across 5 tools
Each tool targets a distinct action: health check, API key validation, app listing, polling incoming messages, and sending messages. Descriptions clearly differentiate the purpose of each tool, with no meaningful overlap.
All tools follow a consistent pattern: the 'privacyflow' prefix followed by a verb_noun structure (check_health, verify_api_key, list_apps, poll_messages, send_messages). This uniform naming makes the toolset predictable and easy to navigate.
With exactly 5 tools, the server is well-scoped for a messaging integration service. Each tool covers a necessary operation (health, auth, discovery, receive, send) without unnecessary bloat or redundancy.
The toolset covers the core lifecycle of a messaging service: authentication, app discovery, sending, and receiving messages. Minor gaps exist (e.g., no explicit message acknowledgment or per-app filtering on poll), but these are reasonable workarounds and do not cripple the primary workflows.