9,184 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
MCP server for natural-language queries against SAP CAP db-layer entities via real CQN/SQL JOINs. Runs locally from the @shahid.la/cds-db-nlquery-mcp npm package. Needs 4 environment variables to run.
★not rated 0 1mo agoA
tokens not measured
originalMIT
MCP server for Directus 12 — items, collections, files, flows, users, and schema tools. Runs locally from the @staminna/directus-mcp-server npm package. Needs 2 environment variables to run.
★not rated 0 17d agoA
tokens not measured
originalMIT
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP. Runs locally from the @upstash/redis-mcp npm package. Needs 3 environment variables to run.
★not rated 0 2mo agoA
tokens not measured
originalMIT
MCP server "sqlbot-mcp-proxy" as configured in wenRou21/sqlbot-mcp-proxy. Runs in Docker (ghcr.io/wenrou21/sqlbot-mcp-proxy:0.1.0). Needs 4 environment variables to run.
★not rated 0 2mo agoA
tokens not measured
originalMIT
MCP server "mysql" as configured in affannahmed/MCP-Server-with-Claude-Ai. Launched with mysql_mcp_server.exe --directory E:/Pycharm/Scripts. Needs 5 environment variables to run.
★not rated 0 1y agoA
tokens not measured
originalMIT
Rules for using the Model Context Protocol, a standard that lets AI models interact with external tools and resources. In this project, those tools provide access to an EdgeDB database, which stores application data.
This is a simple example server implementing a To-Do list CRUD API using the Model Context Protocol (MCP) concepts, specifically using JSON-RPC 2.0 over HTTP. It uses Node.js, Express, and PostgreSQL (via Docker) for persistence.
Lets the agent query and modify a local SQLite database. Runs locally from the mcp-server-sqlite npm package.
★not rated 0 11mo agoA
tokens not measured
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: