Ext Ops Panel
Open dashboard
Comparison

TasteMaker vs btlabs Core

TasteMaker is an MCP server published by tastemakerdev.com. Marketplaces we read that list it: 1 (Official MCP Registry). btlabs Core is an MCP server published by btlabs.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceTasteMakerbtlabs Core
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.1
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

TasteMaker vs btlabs Core
FactTasteMakerbtlabs Core
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (tastemakerdev.com/mcp)Remote server (btlabs.dev/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/ryan-the-brodsky/tastemakerNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13Responded 10 h ago, requires a key

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

TasteMaker

In its own words, on Official MCP Registry:

Pull your TasteMaker brand kit + generated Agent Skill into your coding tool. Read-only.

btlabs Core

In its own words, on Official MCP Registry:

btlabs Core MCP endpoint: site content and brand data for AI agents. OAuth or API key.

How to run each

TasteMaker As a remote MCP server

Claude Code
claude mcp add --transport http tastemaker https://tastemakerdev.com/mcp/

btlabs Core As a remote MCP server

Claude Code
claude mcp add --transport http core https://btlabs.dev/api/mcp

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

Only the endpoint of btlabs Core responded at the last daily 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: TasteMaker · What it can do: btlabs Core · Compare two other plugins

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