theorapy vs ai.getthroughline/throughline
theorapy is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
theorapy is a plugin bundle for AI coding tools published by anshul-dying. No marketplace we read lists it any more. ai.getthroughline/throughline is an MCP server published by getthroughline.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ai.getthroughline/throughline | |
|---|---|---|
| Community marketplace anshul-dying/theorapy | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | theorapyno longer listed · | ai.getthroughline/throughline |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (getthroughline.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/anshul-dying/theorapy | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of theorapy
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Now your agents can ask a therapist same way as humans.
-
Make your AI agent get stronger with use. Includes two skills: /skill-review (periodic audit of all skills for staleness, missing gotchas, and improvements) and…
-
Chat with your Zihin.ai agents, list them and load platform skills from any MCP client.
-
Give your AI agents the ability to ask real users why.
-
Self-Mirror consciousness loop for human-like AI responses. Adds inner dialogue (Self → Mirror → Conscious Response) to make AI output feel authentic, not robotic. Zero…
-
VerifiMind PEAS - RefleXion Trinity
X-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.66
What each says it does
theorapy
Therapy for your AI agent: a role-reversal bit where the human is the therapist and the agent is the (fictional) patient.
ai.getthroughline/throughline
A persistent AI self you own — memory, persona, judgment — portable across all your AI hosts.
How to run each
theorapy
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ai.getthroughline/throughline As a remote MCP server
claude mcp add --transport http throughline https://getthroughline.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ai.getthroughline/throughline has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: theorapy · What it can do: ai.getthroughline/throughline · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.