FeedMob MCP Server
# FeedMob MCP Server
MCP (Model Context Protocol) server for the FeedMob Assistant Internal API. Enables AI assistants like Claude to access FeedMob data.
[](https://www.npmjs.com/package/feedmob-mcp-server)
## Quick Start
### Using npx (Recommended)
```bash
# Set your API token
export FEEDMOB_API_TOKEN="your-api-token-here"
# Run directly with npx
npx feedmob-mcp-server
```
### Global Installation
```bash
npm install -g feedmob-mcp-server
# Then run
feedmob-mcp-server
```
### Local Development
```bash
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
```bash
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
Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:
```json
{
"mcpServers": {
"feedmob": {
"command": "npx",
"args": ["feedmob-mcp-server"],
"env": {
"FEEDMOB_API_TOKEN": "your-token"
}
}
}
}
```
## Available Tools
| Tool | Description |
|------|-------------|
| `list_clients` | List clients with filters |
| `get_client` | Get client details by ID |
| `list_client_documents` | List client documents |
| `list_partners` | List partners with filters |
| `get_partner` | Get partner details by ID |
| `list_partner_categories` | List partner categories |
| `list_partner_documents` | List partner documents |
| `list_campaigns` | List campaigns with filters |
| `get_campaign` | Get campaign details by ID |
| `list_playbooks` | List playbooks |
| `get_playbook` | Get playbook with items |
| `get_playbook_item` | Get playbook item content |
| `list_mobile_apps` | List mobile apps |
| `get_mobile_app` | Get mobile app details |
| `list_click_urls` | List click URLs |
| `get_click_url` | Get click URL by legacy ID |
| `get_daily_metrics` | Get daily metrics time-series |
| `list_pods` | List organizational pods |
## License
MIT
TDQS
Scored across 18 tools
Every tool has a clearly distinct purpose targeting specific resources (campaigns, clients, metrics, etc.) with no overlap. The 'get_' tools retrieve single entities by ID, while 'list_' tools return collections with filters, creating a clean separation. An agent can easily distinguish between tools like get_campaign and list_campaigns based on whether they need details or a filtered list.
All tools follow a consistent verb_noun pattern with perfect uniformity. The 'get_' prefix is used for retrieving single entities, and 'list_' for collections, applied consistently across all resources (campaigns, clients, partners, etc.). This predictable naming makes it easy for agents to infer tool purposes and navigate the set.
With 18 tools, the count is slightly high but reasonable for a comprehensive advertising/campaign management domain. It covers multiple resource types (campaigns, clients, partners, playbooks, etc.) with both detail and listing operations, avoiding bloat. A minor reduction might streamline it, but each tool earns its place by serving a distinct function.
The tool set provides strong coverage for a FeedMob advertising platform, including core CRUD-like operations (get and list) for key entities like campaigns, clients, and partners. Minor gaps exist, such as missing update/delete tools or campaign creation, but agents can work around these for read-heavy use cases. The inclusion of metrics, documents, and playbooks adds useful breadth.