Panda CSS MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Structured MCP access to the Panda CSS compiler: Which compiler operations remain available as Panda evolves, and are their schemas documented beyond the short README?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI-assisted Panda CSS compiler and project workflows

What we know

MCP server giving assistants structured access to the Panda CSS compiler.

Maintenance / activity evidence

@pandacss/mcp 2.1.1 published 2026-10-02T18:52:37.189Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Panda CSS/project access as exposed by server. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Project source/configuration

Developer-tool access appears local, but exact tool/write scope needs one source-level verification.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 791.6k package downloads / 30 days

Downloads observed Sep 25, 2026.

30-day package downloads intentionally left null because the package-stats provider ran out of credits during Batch 3 QA.

All limitations / Review context

Which compiler operations remain available as Panda evolves, and are their schemas documented beyond the short README?

The bounded review of the publisher's documented Structured MCP access to the Panda CSS compiler and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Developer-tool access appears local, but exact tool/write scope needs one source-level verification.
Panda CSS/project access as exposed by server.
Project/compiler context processed locally.
Sensitive access: Project source/configuration
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Repository identity
Exact tool inventory
Write scope
Exact tool inventory and auth surface were not fully established from the package page.

Original activity observations

@pandacss/mcp 2.1.1 published 2026-10-02T18:52:37.189Z

Technical identity

npm/@pandacss/mcp

Exact implementation source: https://www.npmjs.com/package/@pandacss/mcp ↗
Reviewed resource type: MCP Server
Package identity: @pandacss/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

Package registry ↗
@pandacss/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Publisher documentation reviewed; compatibility with user environment and live service not tested.
Targeted 2026-10-13 re-research: Publisher confirms npx -y @pandacss/mcp usage; setup requires a compatible PandaCSS project context.
Publisher confirms npx -y @pandacss/mcp usage; setup requires a compatible PandaCSS project context.
Documented by publisher; environment and client prerequisites still required. Placeholder values must not be executed verbatim.
MCP100 normalized publisher npm README command/config; placeholders are NOT real secrets; no client/runtime validation.
Never test by purchase, publication, deletion, financial transfer, sending or account mutation.
Never paste credentials into chat.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.

Install / connect
Publisher instructions
Publisher documents usage but no detailed client-specific configuration; treat stdio link as conditional.
publisher install or stdio launch · Publisher instructions
npx -y @pandacss/mcp
Configure / authenticate
MCP100 setup guide
Keyless Panda CSS MCP package. In a stdio-compatible host, register command npx with args ["-y", "@pandacss/mcp"]; no vendor authentication steps documented.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "panda": { "args": [ "-y", "@pandacss/mcp" ], "command": "npx" } } }
Check connection
Suggested check
Official README documents npx server command but no product-specific health/status tool. Register the npx command with a compatible MCP host and inspect the tool list; host-composed verification, not publisher-certified health command.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `panda`, run `claude mcp remove panda` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Panda CSS MCP README has no API credential; provider token revocation not applicable.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove panda

Official Documentation & Sources

What it does

MCP server giving assistants structured access to the Panda CSS compiler.

Capability: Developer Tools
Resource type: MCP Server
Industry: Software & Technology
Best fit: AI-assisted Panda CSS compiler and project workflows

Representative uses

Compiler-oriented Panda CSS workflows
Inspect/use Panda project/compiler information

Limitations

Exact tool inventory and auth surface were not fully established from the package page.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Panda CSS/project access as exposed by server.
Data handling: Project/compiler context processed locally.
Cost: unknown
Risk and cautions: Developer-tool access appears local, but exact tool/write scope needs one source-level verification.

Access scope and cautions

Write actions: Not verified
Sensitive access: Project source/configuration
Risk level: moderate

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Compiler-oriented Panda CSS workflows; Inspect/use Panda project/compiler information.

What setup information is documented?

Recorded installation/entrypoint step: npx -y @pandacss/mcp. Recorded transport: stdio. Prerequisites: Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Panda CSS/project access as exposed by server.

What data-handling boundary should I consider?

Project/compiler context processed locally. Recorded sensitive-access context: Project source/configuration.

What limitations and risks should I check before use?

Developer-tool access appears local, but exact tool/write scope needs one source-level verification. Exact tool inventory and auth surface were not fully established from the package page. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Chakra Systems Inc. is listed as Ecosystem official in MCP100’s current evidence.