An MCP server that enables searching for specific files by name within the current directory and its subdirectories. It uses Server-Sent Events (SSE) to provide a find_file tool for locating local files and libraries.
MCP server deployed on EdgeOne Pages, providing a Streamable HTTP MCP server for intelligent chat applications with tool capabilities like generating webpages.
A comprehensive Model Context Protocol (MCP) server implementing the latest MCP specification with tools, resources, prompts, and enhanced sampling capabilities that features HackerNews and GitHub API integrations for AI-powered analysis.
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.
Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.
Converts REST API code (like NestJS controllers or FastAPI endpoints) to Postman collections and environments, helping developers automatically sync their API endpoints with Postman.
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.
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.
Enables MCP clients to connect over HTTP and access its MCP resources, with Docker-based deployment and health-check endpoints for reverse-proxy setups.
Enables existing Express routers to be exposed as MCP tools, dispatching tool calls through the Express middleware stack in-process without a network hop.