home / mcp / feedmob mcp server

FeedMob MCP Server

Provides authenticated access to FeedMob data via MCP, enabling queries for clients, partners, campaigns, playbooks, and more.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "hlee-femini-tokyo-mcp": {
      "command": "npx",
      "args": [
        "feedmob-mcp-server"
      ],
      "env": {
        "FEEDMOB_API_TOKEN": "your-token",
        "FEEDMOB_API_BASE_URL": "https://assistant.feedmob.ai"
      }
    }
  }
}

FeedMob MCP Server enables AI assistants to securely access FeedMob data through the Model Context Protocol. It provides a lightweight runtime that exposes FeedMob APIs to clients like Claude, enabling powerful data-driven interactions while keeping authentication and data access centralized and manageable.

How to use

You consume this MCP server by running it as a local process or via an MCP client that communicates through the MCP protocol. Before you start, set your API token so the server can authenticate to FeedMob. You can run the server directly with npx, install it globally, or run it from a local development setup. Use the standard environment variable FEEDMOB_API_TOKEN to supply your token.

How to install

Prerequisites: you need Node.js and npm installed on your workstation.

# Set your API token
export FEEDMOB_API_TOKEN="your-api-token-here"

# Run directly with npx
npx feedmob-mcp-server

Additional setup and configuration

You can also install the MCP server globally and run it from anywhere, or set up a local development environment to contribute or test changes.

# Global installation
npm install -g feedmob-mcp-server

# Then run
feedmob-mcp-server

Local development workflow

For development you can clone the project, install dependencies, build, and run the compiled output.

git clone https://github.com/hlee/femini-tokyo-mcp.git
cd femini-tokyo-mcp
npm install
npm run build
node dist/index.js

Environment variables

Configure the API access and default base URL for the FeedMob internal API.

export FEEDMOB_API_TOKEN="your-api-token-here"
export FEEDMOB_API_BASE_URL="https://assistant.feedmob.ai"  # Optional, this is the default

Claude for Desktop configuration

If you use Claude on desktop, add the MCP server configuration to Claude's config so it can route queries through the FeedMob MCP server.

{
  "mcpServers": {
    "feedmob": {
      "command": "npx",
      "args": ["feedmob-mcp-server"],
      "env": {
        "FEEDMOB_API_TOKEN": "your-token"
      }
    }
  }
}

Available tools

list_clients

List clients with optional filters to refine the results.

get_client

Retrieve detailed information for a single client by its ID.

list_client_documents

List documents associated with a client.

list_partners

List partners with optional filters to refine the results.

get_partner

Retrieve detailed information for a single partner by its ID.

list_partner_categories

List categories for partners.

list_partner_documents

List documents associated with a partner.

list_campaigns

List campaigns with optional filters.

get_campaign

Retrieve details for a specific campaign by ID.

list_playbooks

List available playbooks.

get_playbook

Get a playbook with its items.

get_playbook_item

Get the content of a specific playbook item.

list_mobile_apps

List mobile applications linked to FeedMob.

get_mobile_app

Retrieve details for a specific mobile app by ID.

list_click_urls

List click URLs used for tracking.

get_click_url

Get a click URL by legacy ID.

get_daily_metrics

Fetch daily metrics time-series data.

list_pods

List organizational pods.