Thoth MCP

Hibiki MCP Server

Model Context Protocol (MCP) server for Hibiki content creation platform. This server enables AI assistants and tools to create and retrieve content through Hibiki's API.

✨ NEW: Claude Code Plugin now available with slash commands and specialized AI agents for streamlined content creation workflows!

Quick Start

# Install via npx

npx @hibiki/mcp-server --api-key YOUR_API_KEY

Or configure in Claude Desktop (see Configuration below)

Get your API key at www.gethibiki.com/settings/api-keys

Table of Contents

• Quick Start
• Features
• Claude Code Plugin
• Installation
• Usage
• MCP Client Configuration
• Available Tools
• Available Resources
• Development
• API Integration
• Examples
• Troubleshooting
• Contributing
• Support
• Changelog

Features

• Create Content: Generate platform-optimized content with AI enhancement
• Retrieve & Manage Posts: Fetch, list, and update post data with pagination
• Multi-Platform Support: Twitter, Instagram, LinkedIn, Facebook, Threads, Blog, Reddit
• Brand Styles: Apply consistent voice, tone, and visual styling with brand presets
• Image Generation: Optionally generate images for your content
• Scheduling: Schedule posts for future publication
• Dual Transport: Supports both stdio (local) and HTTP transports (Smithery/cloud deployment)
• Type-Safe: Built with TypeScript and Zod validation

Claude Code Plugin

NEW! We've created an official Claude Code plugin that makes social media content creation even easier with user-friendly commands and specialized AI agents.

What is it?

The Hibiki plugin for Claude Code provides:

• 5 Slash Commands: Quick access to common workflows
• /create-content - Create multi-platform posts with AI guidance
• /schedule-post - Schedule posts for optimal engagement times
• /view-brands - Browse and manage your brand styles
• /manage-posts - List, filter, and manage all your posts
• /preview-post - Preview platform-specific content formatting

• 3 Specialized Agents: Expert AI assistants for specific tasks
• Content Creator - Expert at crafting engaging, platform-optimized content
• Brand Manager - Ensures brand consistency across all platforms
• Social Media Optimizer - Maximizes reach and engagement through data-driven strategies

Quick Start with Plugin

# Install the plugin

claude plugin install hibiki

Set your API key

export HIBIKI_API_KEY="your-api-key-here"

Start creating content

claude /create-content "Announcing our new feature"

Or use an agent

claude "Content Creator, help me announce our product launch"

Documentation

Full plugin documentation, installation instructions, and usage examples are available in the claude-code-plugin directory.

See claude-code-plugin/README.md for:

• Detailed installation instructions
• Complete command reference
• Agent usage guides
• Advanced workflows and examples
• Troubleshooting tips

Installation

Via MCP Registry (Recommended)

The server is published in the official MCP Registry as io.github.gethibiki/mcp.

Browse and install via the registry web interface, or configure directly in your MCP client (see MCP Client Configuration below).

Via Smithery (Zero-Setup Deployment)

The easiest way to get started is through Smithery, which provides:

• One-click installation - No local dependencies or configuration needed
• Automatic updates - Always get the latest version
• Secure hosting - Your API keys are safely managed
• Interactive playground - Test tools before using them

Install from Smithery:

1. Visit the Hibiki MCP Server on Smithery
2. Click "Install"
3. Enter your Hibiki API key when prompted
4. Start using immediately in Claude Desktop or other MCP clients

Global Installation (via npx)

npx @hibiki/mcp-server --api-key YOUR_API_KEY

Local Development

git clone https://github.com/gethibiki/mcp.git

cd hibiki-mcp pnpm install pnpm build

Usage

Prerequisites

You'll need a Hibiki API key. Generate one at:

• Production: https://www.gethibiki.com/settings/api-keys
• Development: http://localhost:3000/settings/api-keys

Running the Server

Stdio Mode (Local)

This is the default mode for use with MCP clients like Claude Desktop:

npx @hibiki/mcp-server --api-key YOUR_API_KEY

Or debug with MCP Inspector:

npx @modelcontextprotocol/inspector npx @hibiki/mcp-server --api-key YOUR_API_KEY

With custom base URL:

npx @hibiki/mcp-server \

--api-key YOUR_API_KEY \ --base-url https://www.gethibiki.com

Remote HTTP Server Mode

Run the server in HTTP mode for cloud deployments (like Smithery) or to expose the server over HTTP:

npx @hibiki/mcp-server --remote --api-key YOUR_API_KEY

The server will start an HTTP server on port 8081 (configurable via PORT environment variable) with:

• /mcp - Main MCP endpoint (POST)
• /health - Health check endpoint (GET)

With custom configuration:

PORT=3000 npx @hibiki/mcp-server \

--remote \ --api-key YOUR_API_KEY \ --base-url https://www.gethibiki.com

Note: In HTTP mode, the server implements MCP Streamable HTTP transport with proper CORS configuration for browser-based clients.

Environment Variables

Instead of command-line flags, you can use environment variables:

For stdio mode:

export HIBIKI_API_KEY=your_api_key

export HIBIKI_BASE_URL=http://localhost:3000 npx @hibiki/mcp-server

For HTTP mode:

export HIBIKI_API_KEY=your_api_key

export HIBIKI_BASE_URL=https://www.gethibiki.com export PORT=8081 npx @hibiki/mcp-server --remote

Available environment variables:

• HIBIKI_API_KEY - Your Hibiki API key (stdio mode only; HTTP mode uses query params)
• HIBIKI_BASE_URL - Base URL for Hibiki API (default: https://www.gethibiki.com)
• PORT - HTTP server port (HTTP mode only, default: 8081)

MCP Client Configuration

Claude Desktop

Add to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%/Claude/claude_desktop_config.json

{

"mcpServers": { "hibiki": { "command": "npx", "args": [ "@hibiki/mcp-server", "--api-key", "YOUR_API_KEY", "--base-url", "http://localhost:3000" ] } } }

Other MCP Clients

For other MCP clients that support stdio transport, use a similar configuration with appropriate command and args.

Available Tools

The server provides 6 tools for managing Hibiki content:

create-post

Create a new content post with platform-specific variations.

Parameters:

• content (required): The original content to be enhanced
• platforms (required): Array of target platforms
• Options: twitter, instagram, linkedin, facebook, threads, blog, reddit
• length (optional): Content length - very-short, short, medium, long (default: medium)
• createImage (optional): Generate an image (default: false)
• createHashtags (optional): Generate hashtags (default: true)
• scheduleTime (optional): ISO 8601 datetime to schedule the post
• postToSocialNetworks (optional): Immediately post to connected networks (default: false)
• brandStyleId (optional): Brand style UUID to apply

Example:

{

"content": "Just launched our new AI-powered content creation tool!", "platforms": ["twitter", "linkedin"], "length": "medium", "createImage": true, "createHashtags": true }

Returns:

• Post ID
• Original content
• Platform-specific enhanced content
• Generated images (if requested)
• Hashtags for each platform
• Status and timestamps

get-post

Retrieve a post by its ID.

Parameters:

• postId (required): UUID of the post

Example:

{

"postId": "123e4567-e89b-12d3-a456-426614174000" }

Returns:

• Complete post data
• Platform-specific content
• Generated images
• Status and metadata

get-all-posts

List all posts with pagination and filtering.

Parameters:

• page (optional): Page number (default: 1)
• limit (optional): Posts per page (default: 10)
• status (optional): Filter by status - draft, scheduled, published

Example:

{

"page": 1, "limit": 20, "status": "published" }

Returns:

• Array of posts with metadata
• Pagination information
• Total count

update-post

Update an existing post.

Parameters:

• postId (required): UUID of the post to update
• title (optional): New title for the post
• content (optional): New content
• status (optional): New status - draft, scheduled, published

Example:

{

"postId": "123e4567-e89b-12d3-a456-426614174000", "title": "Updated Title", "status": "published" }

Returns:

• Updated post data
• Confirmation message

get-brand-styles

List all available brand styles for your account.

Parameters: None

Returns:

• Array of brand styles with IDs and names
• Style metadata

get-brand-style

Get details for a specific brand style.

Parameters:

• brandStyleId (required): UUID of the brand style

Example:

{

"brandStyleId": "123e4567-e89b-12d3-a456-426614174000" }

Returns:

• Brand style name and description
• Color palette
• Typography settings
• Tone and voice guidelines
• Imagery preferences

Available Resources

post://{postId}

Access post data as an MCP resource.

Example URI:

post://123e4567-e89b-12d3-a456-426614174000

preview://{postId}/{platform}

Get platform-specific preview content.

Example URI:

preview://123e4567-e89b-12d3-a456-426614174000/twitter

Development

Building

pnpm build

Running Locally

pnpm start -- --api-key YOUR_API_KEY

Type Checking

pnpm typecheck

Development Mode (Watch)

pnpm dev

API Integration

The MCP server connects to Hibiki's REST API endpoints:

• POST /api/v1/posts - Create new posts
• GET /api/v1/posts/{postId} - Retrieve single post
• GET /api/v1/posts - List posts with pagination
• PUT /api/v1/posts/{postId} - Update existi