"How to send Chrome network and console logs to Cursor editor" matching MCP servers:

Enables Cursor AI to read and modify Figma designs programmatically via the Model Context Protocol.

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.

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

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

An MCP server integration that enables Cursor AI to communicate with Figma, allowing users to read designs and modify them programmatically through natural language commands.

Enables Cursor AI to interact with Figma designs, allowing users to read design information and programmatically modify elements through natural language commands.

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

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 Cursor AI to read and modify Figma designs via the Model Context Protocol, allowing programmatic control over documents, components, styles, and more.

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 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.

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 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 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.

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.

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.

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

A local MCP server for Cursor that converts Markdown files and Mermaid diagrams to JPEG images with configurable dimensions and quality.

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

Allows Cursor AI to communicate with Figma for reading designs and modifying them programmatically through a Model Context Protocol integration.

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.

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.

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.

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.