Developer Overview
Integrate Brandmanna with your tools using API keys, MCP, and webhooks.
Brandmanna provides three integration points that let you connect the platform to your existing tools and workflows. Whether you want to manage content from an AI assistant, automate publishing pipelines, or build custom integrations, you have the tools to do it.
API Keys
API keys give you authenticated, programmatic access to Brandmanna. You need an API key to connect the MCP server, authenticate webhook payloads, or build any custom integration.
You can generate up to 5 active keys from your Account Settings. Each key is shown once at creation and stored securely as a SHA-256 hash. Keys use the manna_ prefix for easy identification.
When you need an API key
- Connecting the Manna MCP Server to Claude Desktop, Cursor, or VS Code.
- Configuring webhook signature verification for Zapier, Make.com, or n8n.
- Building custom scripts that interact with the Brandmanna API.
Quick setup
- Go to Account Settings > API Keys.
- Click Create New Key and give it a descriptive name.
- Copy the key immediately — it is shown only once.
MCP Server
The Manna MCP Server connects Brandmanna to AI assistants that support the Model Context Protocol. You can manage brands, generate content, create plans, and publish posts — all through natural language conversation.
Supported clients
- Claude Desktop — Anthropic's desktop app for macOS and Windows.
- Cursor — AI-powered code editor with built-in MCP support.
- VS Code — Microsoft's editor via the MCP extension.
What you can do
Once connected, your AI assistant has access to 13 tools covering brand management, content generation, draft refinement, scheduling, publishing, and calendar intelligence. You also get read-only resources for brand profiles and guided prompts for common workflows.
Quick setup
- Generate an API key (see above).
- Install the server:
pip install manna-mcpor run withuvx manna-mcp. - Add the configuration to your AI client's MCP settings.
Webhooks
Webhooks let you push draft content to external tools whenever you click "Send to Connected Apps" on a draft. Brandmanna sends a signed JSON payload to your configured URL with the full draft content, platform, brand info, image URL, scheduling details, and a link back to the editor.
Supported destinations
- Zapier — Use the "Webhooks by Zapier" trigger to start any zap from content events.
- Make.com — Create scenarios with a "Custom Webhook" trigger module.
- n8n — Add a Webhook node as your automation trigger.
- Custom HTTP endpoints — Any server that accepts POST requests with JSON.
Security
Each webhook payload includes an HMAC-SHA256 signature in the X-Webhook-Signature header. Your receiving endpoint can verify this signature using the secret token generated during webhook setup, ensuring that requests are genuinely from Brandmanna.
Quick setup
- Go to the Brands page and select a brand.
- Open the webhook configuration section.
- Enter your webhook URL and save the generated secret token.
- Click Test Webhook to verify the connection.
Next Steps
- API Keys — Create and manage your keys.
- MCP Server — Set up Claude Desktop, Cursor, or VS Code.
- Webhooks — Connect to Zapier, Make, n8n, or custom endpoints.
- Account Settings — Manage all integration settings from one place.
- FAQ — Answers to common integration questions.