Search Results for "http"

DBHub is a universal database gateway that implements the MCP server interface so assistants and IDEs can explore and query databases through typed tools. It supports multiple transports—stdio for desktop clients and HTTP for networked scenarios—making it flexible to embed or deploy. Configuration is environment-variable driven, with a DSN and per-engine settings covering Postgres, MySQL, MariaDB, SQL Server, and SQLite. Operational flags include read-only mode, row limits, and even SSH tunneling options for secure access into private networks. A demo mode ships with an in-memory SQLite “employee” dataset so users can try the tools immediately without provisioning a database. ...

mcp-proxy is a lightweight bridge that converts between MCP transports, letting you run a server on stdio and expose it over Streamable HTTP (SSE) or do the reverse. This enables existing desktop-style MCP servers to be reused by web services and IDEs that prefer HTTP, without modifying the server. The tool can multiplex multiple named STDIO servers behind one proxy instance, simplifying fleet deployments or local development with many tools. It ships prebuilt artifacts and a Homebrew formula for quick install on macOS and Linux, with container images published for broader environments. ...

MCPHub is a unified hub that organizes many MCP servers behind clean Streamable HTTP (SSE) endpoints so clients can connect to “all tools,” a specific server, or logical groups. It’s designed to simplify multi-server operations: one process can multiplex several named STDIO servers and re-expose them over HTTP for IDEs and services. The README ships in multiple languages and includes deployment and routing guidance, signaling an intention to reach a broad user base.

...Out of the box it exposes more than 20–25 chart generators—covering staples like bar, line, area, histogram and pie, plus advanced visuals such as dual-axes, heatmaps, radar, flow and fishbone diagrams—so an AI client can request a chart and receive an image URL in return. The server can run over stdio for desktop IDEs or via SSE/“streamable” HTTP transport, making it easy to plug into MCP-capable clients and platforms (including Dify) without custom glue code. A simple CLI and environment variables control behavior, including disabling specific tools, selecting a visualization request service, or tagging a service instance for multi-tenant setups. The README documents private deployment, record generation, and tool filtering, giving teams a path from local experimentation to managed usage.

The Apify Actors MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to interact with Apify Actors. This integration allows AI models to utilize various web scraping and automation tools provided by Apify, facilitating tasks such as data extraction and web automation. ​

Unla is a lightweight, highly available MCP gateway written in Go that turns existing MCP servers or ordinary HTTP APIs into MCP-compliant services through configuration, not code changes. Its goal is to let teams “wire up” tools they already run—internal REST endpoints, third-party APIs, or local MCP servers—and present a single, reliable MCP interface to clients like Claude Desktop, Cursor, and IDEs. The gateway focuses on operational concerns you’d expect in production: multi-instance availability, health checking, and declarative routing that maps upstreams to MCP tools and resources. ...

Scholar Sidekick MCP Server gives any MCP-capable AI assistant (Claude, ChatGPT, Cursor, Cline, Continue, and others) six citation tools. From any supported identifier - DOI, PMID, PMCID, ISBN, arXiv ID, ISSN, NASA ADS bibcode, or WHO IRIS URL - it can: - resolveIdentifier - return structured bibliographic metadata (CSL JSON) - formatCitation - format into 10,000+ CSL styles (Vancouver, APA, AMA, IEEE, CSE, or any CSL style ID) - exportCitation - export to BibTeX, RIS, CSL JSON,...