"How to Connect to a Remote Server" matching MCP servers:

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

A Model Context Protocol server that converts Markdown content to HTML format.

Enables an MCP-compatible AI client to author Blender Python, run Blender, import the resulting asset into Unity with materials and a prefab, place it in the active scene, verify the import, and revise the same asset using stable IDs.

Turns any OpenAPI REST or GraphQL API into an MCP server, allowing AI assistants like Claude to interact with APIs without writing code.

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

A bridge that enables any LLM to access and interact with documented REST APIs through the Model Context Protocol (MCP).

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.

Enables users to record, review, verify, and expose permitted browser workflows as callable MCP tools with typed inputs, isolated Chromium verification, and approval-gated writes.

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

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 agents to turn a plain-language description of a device into a complete, validated build package — parts list, 3D-printable parts, wiring, firmware code, picture assembly guide, and tests — that anyone can assemble without electronics experience.

Enables MCP clients to expose selected operations from local OpenAPI 3.0/3.1 documents as tools, with stdio serving or generated standalone server projects and read-only defaults.

Lets AI agents turn a repository's git history into proposed GitHub issues grouped into units of work, each with a commit checklist and links, then create and close them only after approval. Planning is read-only and creation defaults to a dry run, skipping anything that already exists.

Converts any OpenAPI 3.x spec into a live MCP server, making every endpoint a validated tool that AI agents can call without writing glue code.

Converts any REST API endpoints into MCP tools, enabling AI clients like Cursor and Claude Desktop to call internal services directly.

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.

MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.

Routes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.

Converts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.

Turn natural language into 3D models in Fusion 360. 64 CAD tools including sketches, extrudes, fillets,and JIS standard parts.

MCP server that fetches API responses and generates ready-to-use model/POJO classes in your configured language, with built-in login/refresh token handling.

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

This MCP server lets AI agents connect to Figma to read, analyze, create, and modify designs, including elements, styles, assets, and code generation. It works with free Figma accounts and supports parallel multi-agent use across MCP-compatible clients.

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

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.

Exposes any stdio-based MCP server over the MCP Streamable HTTP transport so remote clients can reach it, spawning an isolated child process per session and gating access behind a secret URL path.

An MCP server that adds engineering discipline to AI-assisted development, enforcing evidence-gated TDD, security review, backup strategy, and deployment generation to turn AI-generated code into production-ready software.

Deterministic Markdown-to-Word (.docx) publishing compiler with native OMML equations, three-line tables, CSL citations, and quality gates for AI agents.