"Building an MCP tool to connect to Upwork API and retrieve job listings" matching MCP servers:

A tool that creates MCP (Model Context Protocol) servers from OpenAPI/Swagger specifications, enabling AI assistants to interact with your APIs.

Acts as a bridge between standard REST/OpenAPI web APIs and the Model Context Protocol, dynamically converting REST endpoints into MCP tools for LLM clients like Cursor, Claude Desktop, and n8n.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

A Model Context Protocol server that enables AI agents to search, analyze, and apply for Upwork jobs autonomously. It facilitates specialized job scoring, proposal submission, and integrated client messaging through a combination of browser automation and API access.

Enables existing Express routers to be exposed as MCP tools, dispatching tool calls through the Express middleware stack in-process without a network hop.

Auto-generates MCP tools from your OpenAPI spec, allowing natural language interaction with any API via configurable headers and serverless deployment.

Enables AI agents to transcribe Instagram Reels into text by providing a tool that accepts a Reel URL and returns the speech transcript along with metadata such as author and duration.

Enables AI assistants to call any SOAP/WSDL web service as MCP tools, automatically converting each WSDL operation into a callable tool with authentication and security controls.

A standalone proxy that transforms any OpenAPI or Swagger-described REST API into an MCP server by mapping API operations to executable MCP tools. It enables AI clients to interact with existing web services through automated HTTP requests based on their official documentation.

Enables AI assistants to convert CSS-animated SVGs into videos (MP4/WebM/MKV/MOV) and animated images (aPNG/GIF) with frame-accurate rendering and transparency support.

A Model Context Protocol server that converts Markdown documents to plain text with flexible options and dual protocol support.

An MCP server that enables AI agents to retrieve detailed GitHub Pull Request information using git commit hashes, branch names, or PR numbers. It automatically detects repositories and extracts comprehensive PR data including descriptions, labels, and reviews via the GitHub CLI.

One-pass agentic inbox triage as an MCP server: fetch unread Gmail → classify (action_needed/fyi/newsletter/noise) → summarize → extract tasks → draft replies as Gmail DRAFTS (never sends) → flag calendar → write a triage report. Four stdio tools (fetch_emails, save_gmail_draft, append_tasks, write_report); the host is the LLM, so it runs keyless in Claude Code. Gmail scopes: readonly + compose

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

Enables LLMs to query documents using semantic search, supporting PDFs, Word, Excel, and more. Organizes documents by topics from folder structure and provides advanced search features like phrase matching and date filtering.

Converts any Python Click or Typer CLI into an MCP server automatically — zero-code transformation that introspects CLI commands and exposes them as MCP tools.

Turns any OData V2 or V4 service, SAP Gateway included, into MCP tools that AI clients such as Claude, ChatGPT, Copilot, and Cursor can call without code by reading $metadata. It lets models discover entity sets and fields, then query services through built-in read-only tools.

A minimal MCP server that auto-generates tools from your OpenAPI spec, optimized for Vercel.

Turns any OpenAPI/Swagger or REST API into callable MCP tools for Claude, ChatGPT, Copilot, and Cursor, with secure authentication and role-based access control.

Enables agentic co-authoring of feature specs, decomposition into architecture-validated tickets, and idempotent syncing to Linear as projects with epics, sub-issues, and dependencies.