"A platform or tool for applying to jobs" matching MCP servers:

Enables LLMs to perform addition calculations through a stdio-based MCP server with an add_numbers tool and type-safe validation.

MCP server for job search that crawls job listings using Playwright, with a fix for stdout pollution on Windows/WorkBuddy.

Enables AI agents to call tools through a security gateway that intercepts requests, enforces deterministic policy and risk checks, blocks or escalates high-risk actions for human approval, and keeps tool credentials and audit logs protected.

A self-hosted platform that aggregates upstream MCP servers, OpenAPI imports, and remote device connectors behind a single endpoint per profile, with per-agent scoped authorization, tool/prompt/resource catalogs, and approval-based temporary permissions. It also lets administrators distribute skills and connectors to paired devices and export client configurations.

Enables natural-language job search and aggregation from multiple recruitment websites with zero configuration, providing filtered results and standardized output for AI assistants.

A zero-configuration job aggregation server that enables searching for positions and retrieving details across multiple recruitment platforms using natural language. It provides standardized data for job requirements, salary comparisons, and market trends directly within AI clients.

Enables searching for job opportunities across multiple platforms like Upwork, RemoteOK, and GitHub while automatically generating tailored application proposals based on keyword scoring. It includes tools for scanning all sources simultaneously and managing a professional profile for quick reference during applications.

Live open jobs from companies' own Greenhouse, Lever and Ashby boards via their official public APIs, with publish-verified dates, age, long-open and repost signals, filters and change tracking.

MCP server for Argo CD and Vault that allows authenticated users to run CLI commands via GitLab SSO, with confirmation for dangerous operations and secret redaction from model context.

Enables real-time job search across thousands of companies' open roles from Greenhouse, Lever, Ashby, and SmartRecruiters, with full-text filtering and company-specific queries, no API key required.

A tool discovery MCP server that integrates with Azure DevOps wikis and code-graph-rag to match natural language goals to tools, enabling tool composition and proxy testing.

MCP server enabling Claude Code to capture screenshots of Windows applications through WSL2, allowing AI to diagnose UI errors and verify layouts.

Analyzes codebases for cross-platform compatibility issues, detecting platform-specific APIs, file path problems, line ending inconsistencies, and shell command incompatibilities across Windows, macOS, and Linux.

A Model Context Protocol server that provides Google Jobs search capabilities through SerpAPI integration, featuring multi-language support, flexible search parameters, and rich job details.

Enables IDE plugins to authenticate and communicate with the YAAIF platform via MCP, bridging Cursor, VS Code, IntelliJ, Claude Code, Codex, and OpenCode.

A simple MCP server implementation in TypeScript that communicates over stdio, allowing users to ask questions that end with 'yes or no' to trigger the MCP tool in Cursor.

Provides agents with tools to score a page's AI readiness, check which AI crawlers robots.txt blocks, and assess passage citability—all performed locally.

Provides a unified MCP server to interact with multiple middleware (Loki, MySQL, Redis, RocketMQ, Elasticsearch, MongoDB) through a desktop application for connection management and configuration export.

A Node.js and TypeScript server that enables searching for job listings and accessing job market statistics via the Model Context Protocol. It provides tools for job queries and arithmetic operations alongside resources for featured listings and market data.

Turns any OpenAPI spec into a single-tool MCP server where the model writes JavaScript against a typed api object in a QuickJS sandbox, so multi-step tasks run in one round trip and only the final result reaches context. Credentials, rate limiting, retries, write gating and audit logging stay on the host, outside the sandbox.