timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Persistent goals for Claude: standing objectives with items, memory and approvals.
Texto original del autor
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 | 20/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 | 32/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 Quarterdeck y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Quarterdeck o muestra una herramienta de Quarterdeck 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 Quarterdeck
Quarterdeck se instala en tu computadora, pero ChatGPT solo conecta servidores que funcionan en la web
A · Usa una app que pueda conectar Quarterdeck
Claude Code todavía no puede conectar Quarterdeck
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Quarterdeck
Cursor todavía no puede conectar Quarterdeck
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Quarterdeck
VS Code todavía no puede conectar Quarterdeck
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Quarterdeck
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
Segú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 21 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub shannonbay, dueña del repo
Último cambio de código: hoy
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/shannonbay-quarterdeck)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.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
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 hoy, y la última versión (0.32.0) llegó al registro hoy.
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: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
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
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| Este Quarterdeck | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada |
| Necesita clave | No | No | No | No | No | No |
| Se añade con + en Claude | No | Sí | Sí | Sí | No | No |
| Revisiones básicas | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| Licencia | Apache-2.0 | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 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.
Quarterdeck keeps Claude on top of things for you.
One prompt, /goal-new Sell my birdcage on Facebook Marketplace, and it sold for the asking price the next day. Claude wrote and posted the listing, answered five buyers and lined up the pick-up, and every message waited for my OK first.
*How the sale went · the whole sale on video (2 min) · an agent fixing issues on this repo (80 s). Buyers' names are changed and older chats blurred; the opening was re-created with a cleaner prompt, and the rest is screenshots from the real sale.*
Install it in two commands (you need Claude Code and Node.js 22.13+), then type /goal-new in Claude Code:
claude plugin marketplace add shannonbay/Quarterdeck#release
claude plugin install quarterdeck-goals@quarterdeck --scope user
More in the Quickstart.
It's a Claude Code plugin that turns Claude into a personal assistant: it keeps looking after the things you hand it, asks before it does anything you haven't allowed, and remembers what you decided.
You give it goals: "sell my birdcage on facebook marketplace", "fix new issues on my repo", "find me the three best new job ads each week", "turn NZ$200 into more by flipping Marketplace bargains", "clear old installers out of Downloads". Each goal runs on its own schedule in the background of your Claude Code session, on your Claude plan. When it wants to act, it proposes, and you approve or reject from the Goals pane beside your chat, or from your phone.
The idea behind it: persistent intent may matter more than persistent memory. Instead of prompt → act, a goal is an action cycle that keeps going, punctuated only by your approvals and the occasional question.
· 48k tokens · 2m.*A friend's goal selling his old audio gear stops to ask for condition notes and his floor price instead of guessing.*
Start with /goal-new: pick a ready-made goal (maintain my repo, which sets up all the GitHub goals below at once, unsubscribe from mailing lists, a daily news digest, a weekly job scan with your CV, tidy Downloads, inbox triage, keep your GitHub profile current, fix failing CI, triage new GitHub issues, refine new GitHub issues, work on new GitHub issues, review pull requests, flip items on Facebook Marketplace) or type your own. Schedules can be plain words: "30d", "weekdays at 9", "the first of every month".
It started with one prompt: /goal-new Sell my as-new (unused) birdcage on Facebook Marketplace. I live in Tawa, Wellington. The photos are the two newest pictures in my Pictures folder. Price $50, pick-up only. The GIF at the top shows it.
It sold for the asking price the day after the prompt. My part was approving each reply, choosing the buyer and giving the address; the agent never messaged anyone on its own. And no, it didn't give buyers a recipe for cake.
The whole sale on video (2 minutes, with sound and captions):
Selling one thing is a one-off goal, which moves to Done once nothing is left open. The Flipper goal is the standing kind: grow a NZ$200 budget by buying underpriced things on Facebook Marketplace and Trade Me and reselling them for a profit. Watches on Marketplace's free, furniture and appliance listings and on Trade Me start a run when something new is listed. Each run sorts the new titles by name and price alone, opens at most five, looks at every photo, and skips anything that needs a repair, like a freezer whose lid doesn't seal. A deal worth proposing comes with comparable sales, a resale estimate, the fuel for the round trip, the expected profit, a suggested offer and a pick-up time that fits my week. A ledger in its memory keeps the capital, the stock and each flip.
Every message to a seller, offer and purchase waits for my approval. Its first buy was a dryer for NZ$80 on Trade Me that should resell for NZ$150-180, and I pressed Buy Now myself: Claude in Chrome asks a person to confirm a purchase, and a background run has no one to ask.
Quarterdeck's own repo is looked after by two goals made from the ready-made *Work on new GitHub issues* and *Fix failing CI*. Neither has a schedule: each has a watch, a gh command checked every 5 minutes, and a run starts only when it sees something new. Here is the first issue they handled, start to finish:
The run took 2 minutes. The PR says it was opened by a Quarterdeck goal, and the CI goal now watches main for that merge, ready to propose a fix if anything breaks.
An issue anyone can open is an obvious place to hide instructions for an agent, so the Issue Fixer only takes work from the repo's owner, members and collaborators, and it reads only their comments. When anyone else opens an issue, the run sees just the number and the author, and asks you under Needs you whether to work on it before reading a word. Pushing and opening a pull request wait for your approval in Quarterdeck's guard, not only in the instructions: the goal's tool rules name git push and gh pr create, and turn off other writes to GitHub (comments, gh api, gh auth). These rules match command names, so a script that pushes for it gets past them; running goals in a sandbox is on the roadmap.
A new issue often lacks the context to build it well, so a new Issue Fixer asks whether to wait for a refined label, and waits by default. The *Refine new issues* goal (the Issue Refiner) reads each new issue and the code it touches, asks you about every decision it can't settle from the code, and then proposes a spec: what is asked, the files involved, an approach and acceptance criteria. Once you approve, it posts the spec as a comment and adds refined, which starts the fixer. When only the reporter can answer something, it posts their questions instead and adds needs-clarification, and their reply starts it again. Only someone with triage rights can label an issue, so nobody else can label their own issue to get it built. To switch an Issue Fixer you made earlier, ask Claude to replace its "new issues" and "new issues from others" watches with one on issues labelled refined, and to update its instructions from the template.
In front of the refiner, the *Triage new issues* goal (Issue Triage) reads every new issue, whoever opened it, and proposes labels for the whole batch in one item: its kind and priority from your repo's own labels, a likely duplicate, and triaged. Its only write is labels you approved; it never comments, closes or edits an issue. Once a batch is labelled it asks you one question, "Which of these should be refined?", and answering with the numbers adds needs-refinement to just those (adding the label on GitHub does the same). A new Issue Refiner waits for that label by default, so an agent spends a run only on issues you picked:
new issue → Issue Triage → triaged → (you pick) → needs-refinement → Issue Refiner → refined → Issue Fixer → pull request
To have a refiner you made earlier wait for your pick, ask Claude to replace its "issues to refine" and "issues to refine from others" watches with one on issues labelled needs-refinement, and to update its instructions from the template.
Here's another one on video, from a to-do in the pane to the feature working live (80 seconds, with sound and captions). This time the Issue Fixer stopped to ask which of two designs to build before writing any code (issue #17, PR #18):