Ext Ops Panel
Open dashboard
Comparison

chat-auto-exporter vs io.github.irmasemma/postcopilot-mcp

chat-auto-exporter is a plugin bundle for AI coding tools published by christancho. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.irmasemma/postcopilot-mcp is an MCP server published by irmasemma. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacechat-auto-exporterio.github.irmasemma/postcopilot-mcp
Claude Code: claude-plugins-community Listed
Version: 1.0.2
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
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

chat-auto-exporter vs io.github.irmasemma/postcopilot-mcp
Factchat-auto-exporterio.github.irmasemma/postcopilot-mcp
Marketplaces that list it11
Stars (GitHub) (differs)2 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Installs as a plugin bundleRemote server (postcopilot.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/christancho/chat-autoexportergithub.com/irmasemma/postcopilot-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

chat-auto-exporter

In its own words, on Claude Code: claude-plugins-community:

A Claude Code plugin that automatically saves your conversations as readable text files before context compaction and when sessions end. Never lose a conversation again.

io.github.irmasemma/postcopilot-mcp

In its own words, on Official MCP Registry:

Export any public Threads profile's posts, followers & following into Claude, no login or API key

How to run each

chat-auto-exporter As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install chat-auto-exporter@claude-community

io.github.irmasemma/postcopilot-mcp As a remote MCP server

Claude Code
claude mcp add --transport http postcopilot-mcp https://postcopilot.ai/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.irmasemma/postcopilot-mcp has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of chat-auto-exporter nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: chat-auto-exporter · What it can do: io.github.irmasemma/postcopilot-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built