gft vs GPTaria MCP
gft is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
gft is a plugin bundle for AI coding tools published by CL. No marketplace we read lists it any more. GPTaria MCP is an MCP server published by gptaria-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  GPTaria MCP | |
|---|---|---|
| Community marketplace corallips/gft-mcp | Removed on 2026-10-15 Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Downloads/month (npm): 129 Downloads/week (npm): 21 Forks (GitHub): 0 Stars (GitHub): 0 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 | gftno longer listed · | GPTaria MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gptaria-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/corallips/gft-mcp | github.com/gptaria-mcp/gptaria-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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 gft
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Interactive plugin builder for Claude Code - serves as both an example plugin and a tool to create new plugins through guided prompts with specialized builder skills for each…
-
Comprehensive toolkit for developing Claude Code plugins. Includes 7 expert skills covering hooks, MCP integration, commands, agents, and best practices. AI-assisted plugin…
-
Comprehensive toolkit for developing Claude Code plugins. Includes 7 expert skills covering hooks, MCP integration, commands, agents, and best practices. AI-assisted plugin…
-
Let local Claude Code sessions talk to each other in natural language.
-
MCPJungle gateway — connects Claude Code to the essentials tool group at mcp.dhruv.cc
-
Scaffold, validate, and publish new Claude Code plugins with proper structure
What each says it does
gft
GFT for Claude Code: instant /gft:list & /gft:login (zero tokens via hook), /gft:link & /gft:save for connecting thinking maps, MCP server auto-configured
GPTaria MCP
Post a project brief & publish cases on GPTaria from Claude Code, Cursor or Windsurf.
How to run each
gft
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GPTaria MCP As a local MCP server: npm package
claude mcp add --env "GPTARIA_API_KEY=<YOUR_GPTARIA_API_KEY>" --transport stdio gptaria-mcp -- npx -y gptaria-mcpRequires: GPTARIA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of gft publish no settings it asks for, so we do not compare settings.
What it can do: gft · What it can do: GPTaria MCP · 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.