timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Postgres diagnostics and cluster operations for Multigres clusters.
Skills que enseñan a la IA este tipo de trabajo; funcionan junto a este
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 4/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 16/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude, pero hay que preparar algo antes
Sin clave y sin instalar nada · Solo en la app de Claude para computadora (Windows o Mac), no en la web ni en el móvil
Descargar el archivo .mcpb del creador
El archivo .mcpb viene directo del autor; no lo modificamos
Usa Multigres y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Multigres o muestra una herramienta de Multigres en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
ChatGPT todavía no puede conectar Multigres
Multigres se instala en tu computadora, pero ChatGPT solo conecta servidores que funcionan en la web
A · Usa una app que pueda conectar Multigres
B · Otros en Bases de datos y conjuntos de datos que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
Claude Code todavía no puede conectar Multigres
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Multigres
Cursor todavía no puede conectar Multigres
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Multigres
VS Code todavía no puede conectar Multigres
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Multigres
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
DATABASE_URI secreto obligatorio envMULTIGRES_ADMIN_URL envMULTIGRES_ADMIN_TOKEN secreto obligatorio envMULTIGRES_NODE_HOST_MAP envMULTIGRES_MCP_ACCESS_MODE envMULTIGRES_MCP_SQL_TIMEOUT envDescripciones traducidas automáticamente; los nombres de variables quedan como en el original. Si dudas, mira el original.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
mcpb: …/multigres-mcp-0.1.13.mcpbSegún cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 19 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub JoongHyuk-Shin, dueña del repo
Último cambio de código: ayer
Usa Apache-2.0
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
No revisado: solo se pueden revisar paquetes npm y PyPI con versión
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/joonghyuk-shin-multigres-mcp)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: DATABASE_URI, MULTIGRES_ADMIN_TOKEN
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez ayer, y la última versión (0.1.13) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
MCP server for interacting with the Supabase platform
Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
Query and explore 100+ databases through your DBCode connections.
Connect your AI assistants to Keboola and expose your data, transformations, SQL queries, ...
| Este Multigres | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Se instala en tu equipo | En la nube o instalado en tu equipo | Funciona en la nube, sin instalar nada | Se instala en tu equipo | En la nube o instalado en tu equipo |
| Necesita clave | Sí | No | Sí | No | No | No |
| Se añade con + en Claude | No | No | Sí | Sí | No | No |
| Revisiones básicas | 3/3 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| Licencia | Apache-2.0 | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
An MCP server for Multigres clusters. It gives an MCP client two groups of tools:
The server is read-only by default. Write tools are registered only in the unrestricted mode.
It has been tested against a local Multigres Docker cluster built from commit 5fa0f2955ede (2026-11-10, PostgreSQL 17.7, two cells) on Linux with Docker Engine. Other setups have not been tested.
Each release has a multigres-mcp- .mcpb file. It is an MCP Bundle: clients that install bundles ask for the settings under "Configuration" and run the server. It is also a zip file whose server/ directory holds binaries for Linux and macOS on amd64 and arm64 and for Windows on amd64, which any other client can run directly.
Requires Go 1.26 or later.
git clone https://github.com/JoongHyuk-Shin/multigres-mcp
cd multigres-mcp go build -o multigres-mcp ./cmd/multigres-mcp
The server talks MCP over standard input and output. ./multigres-mcp --help prints the options.
packaging/build-mcpb.sh builds the release bundle into dist/. It also needs jq, Node.js and openssl.
Every option can be given as a flag or as an environment variable. A flag wins over the variable.
| Flag | Variable | Default | Meaning |
|---|---|---|---|
--database-url | DATABASE_URI | none, required | Connection string of the Multigres gateway. |
--admin-url | MULTIGRES_ADMIN_URL | none | multiadmin HTTP address. The cluster tools are registered only when it is set. |
--admin-token | MULTIGRES_ADMIN_TOKEN | none | Bearer token for multiadmin started with --enable-auth. |
--node-host-map | MULTIGRES_NODE_HOST_MAP | none | reported=reachable host pairs, comma separated, for the direct node connections of read_node_log and of the node option of diagnose and get_top_queries. multiadmin reports each node's host as the cluster sees it; this replaces a host that the server cannot reach. Ports are not changed. |
--access-mode | MULTIGRES_MCP_ACCESS_MODE | restricted | restricted (read-only) or unrestricted (adds the write tools). |
--sql-timeout | MULTIGRES_MCP_SQL_TIMEOUT | 25s | Statement timeout for the SQL every tool sends. See "Things to know". |
Direct node connections reuse the user, password and database of --database-url and take the host and port from multiadmin.
In the local Docker cluster both nodes report the host localhost, while their Postgres ports are reachable only at the container's address. Find that address in the Multigres checkout with:
docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' "$(docker compose ps -q multigres)"
and pass it as --node-host-map localhost= .
With Claude Code, for the local Docker cluster (replace 172.18.0.2 with the address found above):
claude mcp add multigres -e DATABASE_URI=postgres://postgres:postgres@localhost:15432/postgres -- /path/to/multigres-mcp --admin-url http://localhost:15000 --node-host-map localhost=172.18.0.2
Other clients take the same command, arguments and environment in their server configuration, for example:
{
"mcpServers": { "multigres": { "type": "stdio", "command": "/path/to/multigres-mcp", "args": ["--admin-url", "http://localhost:15000", "--node-host-map", "localhost=172.18.0.2"], "env": { "DATABASE_URI": "postgres://postgres:postgres@localhost:15432/postgres" } } } }
| Tool | Mode | What it does |
|---|---|---|
list_schemas | both | List the schemas. The multigres schema is internal to Multigres. |
list_objects | both | List the tables, views, sequences or extensions of a schema. |
get_object_details | both | Columns, constraints and indexes of a table or view, or details of a sequence or extension. |
execute_sql | both | Run one read-only statement (SELECT, EXPLAIN of a SELECT, or SHOW). In both modes it only reads. |
explain_query | both | The plan of a query, optionally with ANALYZE or with hypothetical indexes. A query with $1 placeholders, as stored in query statistics, gets a generic plan. |
get_top_queries | both | The slowest or most expensive queries, from pg_stat_statements and from the query statistics each gateway keeps, shown separately. |
analyze_workload_indexes | both | Index advice for the workload in pg_stat_statements, by comparing planner costs with hypothetical indexes. Nothing is created. |
analyze_query_indexes | both | The same for up to 10 given queries. |
diagnose | both | Health checks: bloat, vacuum, locks, activity, waits, slow queries, missing indexes, cache, log, index health, sequences, replication and constraints. It starts with the statistics period of the node that answered. |
cluster_status | both, needs --admin-url | Cells, databases, the primary and replicas of each shard with LSN and lag, gateways, orchestrators, recent primary changes, and whether the connected user is a superuser. |
list_backups | both, needs --admin-url | Backups of a shard. |
verify_backups | both, needs --admin-url | Run pgBackRest verify on a shard's backups, which checks that the backups and archived WAL in the repository are valid. It does not run a restore. |
get_backup_job_status | both, needs --admin-url | Status of a backup job. |
read_node_log | both, needs --admin-url | The end of a node's Postgres log, read over a direct connection to that node. |
execute_write_sql | unrestricted | Run one statement that may change data or schema, committed if it succeeds. |
switch_primary | unrestricted, needs --admin-url | Ask Multigres to switch a shard's primary, then report the old and new primary and terms. Multigres may elect the same node again; the tool says so and does not retry. |
create_backup | unrestricted, needs --admin-url | Start a backup and return its job id. |
expire_backups | unrestricted, needs --admin-url | Expire backups with the retention rules configured in the cluster. |
set_postgres_restarts | unrestricted, needs --admin-url | Turn automatic Postgres restarts on a node on or off. |
That is 14 tools in the restricted mode and 19 in the unrestricted mode, or 9 and 10 without --admin-url. diagnose and get_top_queries take an optional node to read one node directly instead of through the gateway, for example the old primary after a failover.
The restricted mode does not register any tool that can write. Writing SQL is a tool of its own, execute_write_sql, so a client permission given to execute_sql never covers a write, even after the server is restarted in the unrestricted mode.
Every statement that execute_sql, explain_query and analyze_query_indexes receive passes these checks. They do not rely on each other: checks 1, 3 and 4 each stop a write on their own.
SELECT, EXPLAIN of a SELECT, or SHOW, and the tree must not contain data-changing statements, SELECT INTO or locking clauses. Functions must be on an allow list (the postgres-mcp list with functions that have side effects removed), and a schema-qualified function must be in pg_catalog.default_transaction_read_only=on.BEGIN TRANSACTION READ ONLY, which is always rolled back.search_path is pinned, and a statement that calls an unqualified function whose name also exists outside pg_catalog is not sent.This covers the statements the model sends and the functions they call directly. The bodies of objects already in the database (views, functions, operators, policies) are trusted and not checked. Against a production database, connect as a read-only role as well. cluster_status shows whether the connected user is a superuser.
Multigres hands pooled Postgres connections from one client to the next. Within the same transaction, the server removes the hypothetical indexes and session advisory locks a tool call may have left on its connection. If that cleanup fails, it ends its own Postgres session rather than hand the state on. execute_write_sql rejects transaction control, session-level SET and RESET, multigres.* settings, hypopg functions, and statements that leave session state behind (temporary objects, PREPARE, LISTEN, DECLARE ... WITH HOLD, LOAD, DISCARD, DO). Session settings (set_config(..., false)) and the random seed (setseed) changed inside the body of a function or trigger are not removed and can reach the next client of that connection; like the other object bodies, they are trusted.
Direct node connections run fixed queries only, never SQL from the model.
The multiadmin address (in full and as host:port), the admin token and the database password are removed from tool results and error messages. The removal replaces text, so a password that is a common word is masked wherever that word appears. A password equal to the user or database name is not masked, because results show those names; the server prints a warning when it starts.
--sql-timeout defaults to 25s because the multipooler ends a transaction's connection when one statement runs past --connpool-user-reserved-inactivity-timeout (default 30s). To use a longer timeout, raise that pooler setting too.execute_sql and execute_write_sql end with a line naming the settings the server set for that call only (statement_timeout, lock_timeout, and for reads search_path), and the statement_timeout its own session had before. The gateway enforces statement_timeout itself without setting it on the node, so the node's pg_settings shows 0 for it while SHOW through the gateway answers with the gateway's value.node option of diagnose and get_top_queries reads another node.--query-metrics-sql-max-bytes (default 4096) without a marker. Plans and index advice use the full pg_stat_statements text or the full statement you give.get_top_queries shows the first 2,000 characters of each pg_stat_statements text and diagnose the first 500, with the full length and the queryid, so one very long statement cannot fill the 50,000-character result. The result says how to read a longer text with execute_sql in pieces of 20,000 characters. The lock check shows the first 500 characters of the waiting and blocking statements. The index advisors analyze the full text but list each skipped or costed query by its first 200 characters and full length, plus the queryid for workload queries, and show the first 500 characters of