timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Supervise a local dev stack — databases, brokers and services declared in an Alphasfile — over MCP.
Skills that teach the AI this kind of work; they work alongside this one
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
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 8/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 20/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use Zordon and tell me what you can do for me, then show me one thing✓ If Claude says it is using Zordon or shows a Zordon tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Zordon yet
Zordon runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Zordon
B · Others in Databases & datasets that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Claude Code cannot connect Zordon yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Zordon
Cursor cannot connect Zordon yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Zordon
VS Code cannot connect Zordon yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect Zordon
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account piotrkowalczuk, which owns the repo
Code last changed yesterday
Uses GPL-3.0
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/piotrkowalczuk-zordon)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.31.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: QueryWeaver, Supabase, Neon, DBCode, Keboola MCP
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
An MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding.
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
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, ...
| This one Zordon | QueryWeaver | Supabase | Neon | DBCode | Keboola MCP | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Installs on your computer | Cloud or install on your computer | Runs in the cloud, nothing to install | Installs on your computer | Cloud or install on your computer |
| Needs a key | No | No | Yes | No | No | No |
| Add with + in Claude | No | No | Yes | Yes | No | No |
| Basic checks | 3/3 | 3/3 | 5/5 | 5/5 | 2/3 | 5/5 |
| License | GPL-3.0 | AGPL-3.0 | Apache-2.0 | MIT | NOASSERTION | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The local stack your inner loop runs against — databases, brokers, proxies and services as fast, disposable host processes, declared once and supervised together. No containers.
Zordon is a supervisor for the local stack your code runs against — the databases, brokers, proxies and services that have to be alive for your code to be exercised for real. It runs them as ordinary host processes instead of containers, declared once in an Alphasfile and supervised together, so standing the stack up, duplicating it, and throwing it away are all cheap.
Three goals shape every decision. Low latency — standing the stack up and re-running sit inside the loop, not around it; iteration shouldn't wait on infrastructure. Resourcefulness — per-stack overhead stays small enough that many agents run side by side, each with a stack real enough to evaluate against rather than a wall of mocks. Guardrails — the Alphasfile doubles as a contract, so the MCP server hands an agent only a narrow, declared surface: bring the stack up, inspect it, run a provision you named, and work through that interface instead of improvising against the host.
Why not containers? Code is increasingly written in a loop — change something, run the real stack against it, read the result, go again, hundreds of times an hour. Containers buy isolation by paying full cold-start and idle-overhead cost on *every* run: right for production, wasteful for a loop. Zordon takes the other side, recovering isolation from per-run workspaces instead of images — so a second stack beside yours, or a tenth, is a non-event.
Declare the whole stack in one Alphasfile:
service "go" "nats" {
git { url = "github.com/nats-io/nats-server" tag = "v2.14.0" }
vars = { client = net::pickport() } # grab a free port, no clashes arguments { values = { main = { p = self.vars.client } } } }
zordon start # resolve, build, bring it up, stream logs until everything is READY
Alphasfile.net::pickport() picks a free port, fs::tmp()/fs::hash() give per-run paths, and services reference each other (service.go.caddy.vars.http) with zero hardcoded wiring. → docszordon workspace create x stands up a second, fully isolated copy of the entire stack — own ports, own dirs — an agent's sandbox beside yours, no port-mapping. → docszordon start returns the moment every service is READY, then keeps the stack alive in the background.zordon clean for teardown.--agent emits terse, structured logs; output is kept signal-dense because when a model reads your logs, tokens are the budget.zordon mcp exposes every command — and every provision — as MCP tools, so an agent can drive the whole stack. → docsAlphasfile plus the MCP surface form a narrow, declared interface between agent and stack — it runs the *named* provisions you defined, not an open shell, so it can't improvise its way around your setup.zordon, alpha, tommy — and nothing else to install, image, or register.Full docs: [https://zordon.io](https://zordon.io) (source in docs/, built with MkDocs Material).
self, cross-service refszordon sudo/plugin installHomebrew (macOS):
brew install piotrkowalczuk/tap/zordon
A release tarball (macOS and Linux, arm64 and amd64) from Releases:
tar -xzf zordon_<version>_<os>_<arch>.tar.gz -C ~/.local/bin zordon alpha tommy
Or from source, if you have a Go toolchain:
go install github.com/piotrkowalczuk/zordon/cmd/...@latest
Every variant installs the same three binaries — zordon, alpha, and the tommy reaper. Keep them in one directory and make sure that directory is on your $PATH: zordon finds alpha via $PATH, and alpha finds tommy only as a sibling of its own executable. See Binaries and layout.
Create an Alphasfile (see examples/simple), then:
zordon start # spawn alpha, push config, stream bringup logs
zordon status # what's running across the whole chain right now? zordon stop # ask alpha to shut its children down and exit zordon clean # run each provision's clean teardown (stack stopped) zordon workspace create x # a parallel, isolated copy of the stack
See the docs for everything else.
zordon mcp runs an MCP server, over stdio by default or over HTTP with --transport=http. It exposes every zordon command — and every provision — as a tool, so an agent can drive your stack and run provisions on demand.
The fastest path is the Claude Code plugin — no manual config:
/plugin marketplace add piotrkowalczuk/zordon
/plugin install zordon@zordon
This registers the zordon mcp server and a skill nudging the agent toward it automatically; see the install how-to.
For other MCP clients, or without the plugin:
The MCP client launches the server; you don't run zordon mcp yourself. With Claude Code, register it from your project directory:
claude mcp add zordon -- zordon mcp
Or add it to your client's MCP config (e.g. .mcp.json):
{ "mcpServers": { "zordon": { "command": "zordon", "args": ["mcp"] } } }
The server resolves the chain from its working directory, so launch the client from the project tree (or pass -e ZORDON_HOME=…). Provisions run inside the live alpha, so zordon start first — or let the agent call the start tool.
To let an agent confined to a container or sandbox drive a host-side stack, serve it over HTTP instead — the client then needs only a URL, with no zordon binary inside the box:
zordon mcp --transport=http --listen 127.0.0.1:7391
See the how-to; note the endpoint is not authenticated yet.
The server advertises its purpose to the agent via MCP instructions (when to reach for these tools), so it should pick them up on its own. To nudge it harder in a zordon-managed repo, add a line to your CLAUDE.md (or AGENTS.md): *"this project's local stack is managed by zordon — use the zordon MCP tools to bring it up, inspect it, and run provisions."*
See the zordon mcp reference and how-to.