YubHub MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUBHUB_API_KEY | Yes | API key from your account page (https://yubhub.co/dashboard/account) | |
| YUBHUB_USER_ID | Yes | Your YubHub user ID | |
| YUBHUB_ADMIN_API_URL | No | API endpoint (defaults to https://api.yubhub.co) | https://api.yubhub.co |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_feedsB | Get all your job feeds |
| create_feedC | Create a new job feed for monitoring career pages |
| get_feedC | Get detailed information about a specific feed including statistics |
| show_feed_dashboardB | Display an interactive dashboard for monitoring a job feed |
| show_all_feeds_dashboardB | Display a comprehensive dashboard showing all feeds with stats, sortable columns, and XML feed links. Modern React UI with dark theme. |
| trigger_feed_runC | Start job discovery for a specific feed |
| update_feedB | Update a feed's name, tag, or source URLs. Use tag to group feeds by site for filtering on the dashboard. |
| delete_feedA | Delete a feed and all associated jobs. This action cannot be undone. |
| delete_jobsA | Delete all jobs for a specific feed. This action cannot be undone. |
| get_feed_scheduleA | Get the automatic run schedule configuration for a feed. Shows if auto-run is enabled, the run interval, and when the next automatic run is scheduled. |
| enable_feed_auto_runA | Enable automatic weekly runs for a feed. The scheduler worker runs hourly and will automatically trigger this feed at the configured interval (default: 7 days for weekly runs). Great for keeping job feeds updated without manual intervention. |
| disable_feed_auto_runA | Disable automatic runs for a feed. The feed will require manual triggering after this. Use this when you want full control over when a feed runs. |
| list_jobsB | Get all jobs for a specific feed, optionally filtered by status |
| get_jobC | Get detailed information about a specific job |
| retry_failed_jobsA | Retry failed jobs for a feed. Jobs that failed during scraping (no content) are re-queued for scraping. Jobs that failed during enrichment (have content) are re-queued for enrichment. |
| get_stats_overviewB | Get high-level statistics: total enriched jobs, companies, and active feeds. |
| get_top_companiesB | Get top companies by enriched job count, with recent activity (last 7d and 30d). |
| get_categoriesB | Get job counts by category/sector with experience level breakdown (entry, mid, senior). |
| get_top_titlesB | Get the most common job titles by volume (top 30). |
| get_title_trendsA | Get titles gaining or losing demand — compares the last 2 weeks vs prior 2 weeks. |
| get_work_arrangementsB | Get work arrangement distribution (remote, hybrid, onsite, etc.). |
| get_experience_levelsB | Get experience level distribution (entry, mid, senior, etc.). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Most tools have distinct purposes, but some overlap exists: 'get_feed' and 'show_feed_dashboard' both provide feed information, and 'list_feeds' and 'show_all_feeds_dashboard' both list feeds. The descriptions clarify differences (detailed stats vs. interactive UI), but an agent might initially confuse them.
Tool names follow a consistent verb_noun pattern throughout, such as 'create_feed', 'delete_feed', 'get_categories', and 'list_jobs'. All tools use snake_case with clear, descriptive verbs, making them predictable and easy to understand.
With 22 tools, the count is borderline high for a job feed monitoring server. While it covers many aspects, it feels slightly heavy and could potentially be streamlined without losing functionality, as some tools might be combined or simplified.
The tool set provides comprehensive coverage for job feed management, including CRUD operations (create, get, update, delete), monitoring (trigger, retry, enable/disable auto-run), and analytics (stats, trends, distributions). No obvious gaps exist; agents can handle full workflows from setup to analysis.