How do I install Pepita?

Pepita is a local plugin. Install it using npm package: @pepitahq/mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Pepita safe to use?

Yes. Pepita passed MCP Marketplace's automated security scan with a score of 9.8/10 (low risk). Every server on MCP Marketplace is security-scanned before it's listed; see the full security report on this page for the findings and permissions.

What credentials does Pepita need?

Pepita requires the following credentials or environment variables: PEPITA_TOKEN, PEPITA_API_BASE. You can find setup instructions on the server detail page.

What AI apps work with Pepita?

Pepita uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Pepita MCP Server

by Pepitahq

Developer ToolsLow Risk9.8MCP RegistryLocal

Free

Server data from the Official MCP Registry

Read, edit, publish, and preview your pepita websites from Claude.

About

Read, edit, publish, and preview your pepita websites from Claude.

Security Report

9.8

Low Risk9.8Low Risk

Valid MCP server (2 strong, 2 medium validity signals). 1 known CVE in dependencies Package registry verified. Imported from the Official MCP Registry.

4 files analyzed · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

pepita bearer token; overrides the token written to ~/.pepita/config.json by `pepita login`.Required

Environment variable: PEPITA_TOKEN

pepita API host. Defaults to https://app.pepita.dev.Optional

Environment variable: PEPITA_API_BASE

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "dev-pepita-mcp-mcp": {
      "env": {
        "PEPITA_TOKEN": "your-pepita-token-here",
        "PEPITA_API_BASE": "your-pepita-api-base-here"
      },
      "args": [
        "-y",
        "@pepitahq/mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Snapshot. Factored out of the private pepita monorepo, built and released from there, and not standalone-buildable. PRs are applied in the monorepo. https://pepita.dev

@pepitahq/mcp

Local MCP server (stdio) for pepita sites. Lets a local Claude (Claude Code / Desktop / the MCP Inspector) read and edit your sites, publish them, and manage shareable preview links — the same things you can do in the editor. Edits show up live in the pepita editor too, so you can move between the chat and the visual editor mid-task.

Prefer the hosted connector? There's a remote, OAuth-authenticated connector at https://mcp.pepita.dev/mcp — nothing to install, just sign in with your pepita account:
claude mcp add --transport http pepita https://mcp.pepita.dev/mcp
(or add it as a custom connector in Claude Desktop / claude.ai). This package is the local alternative — it runs on your machine and works with any MCP client.

Authentication reuses the pepita CLI: run pepita login first (writes ~/.pepita/config.json), or set PEPITA_TOKEN. No separate OAuth.

Use

# one-off, no install:
npx @pepitahq/mcp

# register the local server in Claude Code:
claude mcp add pepita-local -- npx -y @pepitahq/mcp

Tools

Ten tools — five that read your sites, five that write, publish, or manage previews:

Read — list_sites, get_status, list_site_files, read_site_file, list_previews
Write — write_site_file (into the working copy), publish (→ live), and preview links: create_preview, update_preview (push the current site onto an existing link), delete_preview

list_site_files / read_site_file read the working copy by default, the live site (state: "live"), or a specific preview link (preview: "<name>").

Destructive / account-level actions (custom domains, team, billing, deleting a site) are deliberately not exposed — those stay in the editor UI, where their confirmations live. (Deleting a preview link is exposed: it only stops serving, and the version stays restorable from History.)

Env

PEPITA_TOKEN — bearer token (overrides the config file).
PEPITA_API_BASE — API host (default https://app.pepita.dev).
PEPITA_CONFIG_DIR — config dir (default ~/.pepita).

Reviews

No reviews yet

Be the first to review this server!

More Developer Tools MCP Servers

Git

Free

by Modelcontextprotocol · Developer Tools

Read, search, and manipulate Git repositories programmatically

Toleno

Free

by Toleno · Developer Tools

Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.

mcp-creator-python

Free

by mcp-marketplace · Developer Tools

Create, build, and publish Python MCP servers to PyPI — conversationally.

Pepita MCP Server

About

Security Report

Findings (2)

Permissions Required

What You'll Need

How to Install

Documentation

@pepitahq/mcp

Use

Tools

Env

Reviews

No reviews yet

More Developer Tools MCP Servers

Git

Toleno

mcp-creator-python

MarkItDown

MCP Marketplace

FinAgent