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.
이런 작업을 AI에게 가르치는 Skill, 이것과 함께 쓸 수 있습니다
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
목록은 사용 점수(100점 만점)로 정렬되며 구성은 다음과 같습니다
| 인기 | 4/80 | GitHub 별 또는 주간 다운로드: 큰 쪽 60, 작은 쪽 20 |
|---|---|---|
| 최신성 | 12/12 | 30일 안에 릴리스나 코드 변경이 있으면 만점 |
| 응답 중 | 0/8 | 마지막 점검 때 클라우드 엔드포인트가 응답 |
| 사용 점수 | 16/100 |
품질: 기본 점검 3/3개 통과(표시만, 정렬에는 안 씀) · 상승세: 데이터 없음 (급상승 탭에서만 사용)
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
검사 3/3 통과 · 내 컴퓨터에서 실행돼요
먼저: 어떤 AI를 쓰시나요?
쓰는 앱을 고르면 아래에 단계가 나옵니다.
Claude에 연결할 수 있지만 먼저 준비가 필요해요
키 필요 없음, 설치 필요 없음 · 컴퓨터용 Claude 앱(Windows 또는 Mac)에서만 되고 웹이나 모바일은 안 돼요
Multigres을 써서 나에게 무엇을 해 줄 수 있는지 알려 주고, 하나 해 봐✓ Claude가 Multigres을 쓰고 있다고 하거나 답에 Multigres 도구 이름이 나오면 연결된 거예요
메뉴 이름은 2026년 11월 11일에 Anthropic 도움말에서 확인 · 앱 버전에 따라 화면이 조금 다를 수 있어요
ChatGPT는 아직 Multigres에 연결할 수 없어요
Multigres는 내 컴퓨터에 설치해서 쓰지만 ChatGPT는 웹에서 도는 서버만 연결할 수 있어요
A · Multigres에 연결되는 앱 쓰기
B · 데이터베이스 및 데이터셋에서 ChatGPT에 연결되는 다른 서버
같은 분류에서 많이 쓰는 것 중 키 없이 주소만으로 연결되는 것을 골랐어요
Claude Code는 아직 Multigres에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Multigres에 연결되는 앱 쓰기
Cursor는 아직 Multigres에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Multigres에 연결되는 앱 쓰기
VS Code는 아직 Multigres에 연결할 수 없어요
제작자가 컴퓨터용 Claude 앱 설치 파일만 제공해요
A · Multigres에 연결되는 앱 쓰기
DATABASE_URI 비밀 필수 envMULTIGRES_ADMIN_URL envMULTIGRES_ADMIN_TOKEN 비밀 필수 envMULTIGRES_NODE_HOST_MAP envMULTIGRES_MCP_ACCESS_MODE envMULTIGRES_MCP_SQL_TIMEOUT env설명은 자동 번역이며 변수 이름은 원문 그대로입니다. 확실하지 않으면 원문을 확인하세요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
이 서버의 연결 방식과 각 앱의 공식 문서를 바탕으로 했어요. 2026년 11월 10일 확인.
내 컴퓨터에서 실행하는 앱
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 18일 점검
레지스트리 이름이 GitHub 계정 JoongHyuk-Shin 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
코드 마지막 변경: 어제
Apache-2.0 사용
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/servers/joonghyuk-shin-multigres-mcp)질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.
아직 리뷰가 없어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: DATABASE_URI, MULTIGRES_ADMIN_TOKEN
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 어제 변경됐고, 최신 버전(0.1.13)은 오늘 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
같은 카테고리에는: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
같은 카테고리, 다른 제작자, 명령 확인 완료. 공식이 먼저, 그다음 스타 순.
카드 보는 법:↓ 주간 다운로드i★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
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, ...
| 이 항목 Multigres | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| 실행 위치 | 컴퓨터에 설치 필요 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 | 클라우드에서 동작, 설치 불필요 | 컴퓨터에 설치 필요 | 클라우드 또는 컴퓨터 설치 모두 가능 |
| 키 필요 | 예 | 아니요 | 예 | 아니요 | 아니요 | 아니요 |
| Claude에서 +로 추가 | 아니요 | 아니요 | 예 | 예 | 아니요 | 아니요 |
| 기본 점검 | 3/3 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| 라이선스 | Apache-2.0 | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| 가격 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 | 등록 정보에 비용 없음 |
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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