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 |
Capabilities
Features and capabilities supported by this server
| 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 |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/privacyflow-app/privacyflow-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server