How to Set Up BrandGhost MCP Server with Claude Desktop: Developer Guide

This guide covers the technical setup of BrandGhost’s MCP server with Claude Desktop. If you’re a developer or power user who wants to understand exactly what’s happening during configuration, you’re in the right place.

For a gentler introduction to MCP concepts and capabilities, start with the complete MCP social media automation guide. For a quick non-technical setup, see the beginner tutorial.

Prerequisites and Requirements

Before starting, verify you have the following:

Claude Desktop: Download from Anthropic’s website. The application must be version 1.0 or later to support MCP. Check your version in the About menu. Update if needed.

BrandGhost Account with API Access: Sign up at mcp.brandghost.ai if you haven’t already. You’ll need API credentials, which are available in your account settings after registration.

Connected Social Accounts: The MCP server interacts with social platforms through BrandGhost. Connect your desired platforms (Twitter, LinkedIn, Instagram, etc.) through the BrandGhost dashboard before configuring MCP. The MCP server inherits whatever platform connections you’ve established.

System Requirements:

• macOS 10.15+ or Windows 10+
• Node.js 18+ (for local server installation)
• Network access to BrandGhost API endpoints

Installation Options

BrandGhost’s MCP server can run in two configurations: cloud-hosted or local. Choose based on your needs.

Cloud-Hosted Configuration

The simplest option. BrandGhost runs the MCP server infrastructure. You configure Claude Desktop to connect to it using your API credentials.

Advantages:

• No local installation required
• Automatic updates
• Works immediately after configuration

Disadvantages:

• Requires network connectivity
• Less control over server behavior

Local Server Installation

Run the MCP server on your machine. Useful for development, debugging, or environments with specific network restrictions.

To install locally:

npm install -g @brandghost/mcp-server

After installation, verify:

brandghost-mcp --version

You’ll still need BrandGhost API credentials. The local server communicates with BrandGhost’s API to perform social media operations.

Configuring Claude Desktop for MCP

Claude Desktop stores MCP configuration in a JSON file. The location depends on your operating system.

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

If this file doesn’t exist, create it. The basic structure looks like this:

{
  "mcpServers": {
    "brandghost": {
      "command": "brandghost-mcp",
      "args": [],
      "env": {
        "BRANDGHOST_API_KEY": "your-api-key-here"
      }
    }
  }
}

For cloud-hosted configuration, the structure differs slightly:

{
  "mcpServers": {
    "brandghost": {
      "url": "https://mcp.brandghost.ai/v1",
      "headers": {
        "Authorization": "Bearer your-api-key-here"
      }
    }
  }
}

Replace your-api-key-here with your actual API key from the BrandGhost dashboard.

Authentication and API Keys

Your API key authenticates requests from the MCP server to BrandGhost. Generate keys in the BrandGhost dashboard under Settings > API Access.

Best practices for key management:

Environment Variables: Rather than hardcoding keys in the config file, use environment variables. Set BRANDGHOST_API_KEY in your shell profile:

export BRANDGHOST_API_KEY="your-key-here"

Then reference it in the config:

{
  "mcpServers": {
    "brandghost": {
      "command": "brandghost-mcp",
      "env": {
        "BRANDGHOST_API_KEY": "${BRANDGHOST_API_KEY}"
      }
    }
  }
}

Key Rotation: Regenerate keys periodically. The BrandGhost dashboard lets you create new keys and revoke old ones without disrupting active sessions.

Scope Limitations: If available, use keys with minimal required permissions. A key that can only schedule posts is safer than one with full account access.

For detailed security considerations, see the MCP security guide.

Testing Your First Scheduled Post

After configuration, restart Claude Desktop to load the new MCP settings. Open a new conversation and test the connection.

Start with a diagnostic command:

Can you check my BrandGhost connection and list my connected social accounts?

Claude should respond with information from your BrandGhost account. If it shows your connected platforms, the setup is working.

Next, test scheduling:

Schedule a test post to Twitter for tomorrow at 3 PM. Content: "Testing MCP integration - please ignore"

Claude will confirm the scheduled post. Verify in the BrandGhost dashboard that the post appears in your queue. Delete the test post if you don’t want it to publish.

If scheduling works, your setup is complete.

Available MCP Tools

Once connected, Claude has access to several BrandGhost tools through MCP. Understanding what’s available helps you make effective requests.

schedule_post: Create a new scheduled post. Parameters include platform, content, scheduled time, and optional media attachments.

list_scheduled: Retrieve upcoming scheduled posts. Can filter by platform or date range.

cancel_post: Remove a scheduled post before it publishes. Requires the post ID.

update_post: Modify a scheduled post’s content or timing.

list_platforms: Show connected social accounts and their status.

get_post_analytics: Retrieve performance data for published posts.

Claude automatically selects the appropriate tool based on your natural language request. You don’t need to specify tool names directly.

Advanced Configuration Options

Multiple Accounts

If you manage multiple BrandGhost accounts (for different brands or clients), you can configure multiple MCP servers:

{
  "mcpServers": {
    "brandghost-personal": {
      "command": "brandghost-mcp",
      "env": {
        "BRANDGHOST_API_KEY": "personal-account-key"
      }
    },
    "brandghost-business": {
      "command": "brandghost-mcp",
      "env": {
        "BRANDGHOST_API_KEY": "business-account-key"
      }
    }
  }
}

When scheduling, specify which account: “Schedule to my business Twitter account…”

Logging and Debugging

For troubleshooting, enable verbose logging:

{
  "mcpServers": {
    "brandghost": {
      "command": "brandghost-mcp",
      "args": ["--verbose"],
      "env": {
        "BRANDGHOST_API_KEY": "your-key",
        "DEBUG": "brandghost:*"
      }
    }
  }
}

Logs appear in the console where you launched Claude Desktop or in system logs depending on your configuration.

Custom Server Path

If you’ve installed the server in a non-standard location or are developing a modified version:

{
  "mcpServers": {
    "brandghost": {
      "command": "/path/to/your/brandghost-mcp",
      "args": []
    }
  }
}

Timeout Configuration

For slow network conditions, adjust request timeouts:

{
  "mcpServers": {
    "brandghost": {
      "command": "brandghost-mcp",
      "env": {
        "BRANDGHOST_API_KEY": "your-key",
        "REQUEST_TIMEOUT": "30000"
      }
    }
  }
}

Timeout is in milliseconds. Default is 10000 (10 seconds).

Troubleshooting Common Issues

“MCP server not found”

Claude doesn’t see the BrandGhost server. Check:

1. Config file is in the correct location
2. JSON syntax is valid (no trailing commas, proper quoting)
3. Claude Desktop was restarted after config changes
4. For local install, the brandghost-mcp command is in your PATH

“Authentication failed”

API key issues. Verify:

1. Key is correctly copied (no extra spaces)
2. Key hasn’t been revoked in BrandGhost dashboard
3. Environment variable is properly exported if using that method

“Platform not connected”

Trying to post to a platform you haven’t linked in BrandGhost. Connect the platform through the BrandGhost web dashboard first.

“Rate limit exceeded”

Too many requests in a short period. The BrandGhost API has rate limits to prevent abuse. Wait a few minutes and try again. If you consistently hit limits, contact support about your usage patterns.

“Timeout waiting for response”

Network issues or slow API response. Check your internet connection. Try increasing the timeout configuration. If persistent, check BrandGhost status page for service issues.

Server Crashes

If the local MCP server crashes:

1. Check logs for error messages
2. Verify Node.js version meets requirements
3. Try reinstalling: npm install -g @brandghost/mcp-server
4. Report persistent crashes with logs to BrandGhost support

Extending and Customizing

For developers who want to modify or extend the MCP server:

Source Code: The BrandGhost MCP server source is available for inspection. Contact support for access if you need to audit the code.

Custom Tools: You can add custom tools to your local installation. This requires familiarity with MCP tool definitions and the BrandGhost API.

Webhooks: Configure BrandGhost webhooks to receive notifications when posts are published or fail. Useful for automated monitoring.

Next Steps

With your MCP server configured, explore these resources:

• Complete MCP social media guide for conceptual overview
• Creator workflow guide for practical usage patterns
• Security guide for enterprise considerations

For developer support, reach out through BrandGhost’s developer documentation or community channels.

Frequently Asked Questions

Can I run multiple MCP servers simultaneously?

Yes. Claude Desktop supports multiple MCP servers. Each appears as a separate capability source.

How do I update the MCP server?

For cloud-hosted, updates happen automatically. For local installation: ``bash npm update -g @brandghost/mcp-server `` Then restart Claude Desktop.

Can I use this with other Claude interfaces?

MCP support is specific to Claude Desktop currently. The API (claude.ai) and mobile apps don't support MCP connections yet.

Is the local server required?

No. Cloud-hosted configuration works without installing anything locally. Local installation is optional, primarily useful for development or specific network requirements.

How do I completely remove the MCP configuration?

Delete the brandghost entry from your claude_desktop_config.json and restart Claude Desktop. For local installation, also run npm uninstall -g @brandghost/mcp-server.

Where can I report bugs or request features?

Through the BrandGhost support channels or the community forum linked from your dashboard. For MCP-specific issues, include your server version and relevant log excerpts.