MCP server

Connect Pedra to Claude, ChatGPT, Cursor, and any MCP client. The official Model Context Protocol server exposes one tool per Pedra endpoint — virtual staging, renovation, image enhancement, and listing videos — as blocking calls that return the final asset URL.

Official MCP server

Open source, MIT-licensed, and published to npm as @pedra-ai/mcp. It exposes one tool per API endpoint; each tool is a single blocking call that returns the final asset URL(s) — no job IDs to poll. Under the hood it's a thin wrapper over the Pedra Node SDK.

What you can do

Once connected, ask your assistant in plain language — it picks the right tool and returns the finished image or video URL:

"Use Pedra to virtually stage https://example.com/empty-living-room.jpg as a minimalist living room."

"Empty this furnished bedroom so I can show the bare room: https://example.com/bedroom.jpg"

"Renovate this dated kitchen in a Scandinavian style: https://example.com/kitchen.jpg"

"Add a large green plant in the corner of this living room: https://example.com/living.jpg"

"Brighten and straighten the photo I just attached."

"Swap the grey sky in this exterior shot for clear blue: https://example.com/facade.jpg"

"Blur the faces and license plates in this street-facing photo: https://example.com/street.jpg"

"Make a listing video from these 8 photos with music and a '3 bed · 2 bath' caption."

"How many Pedra credits do I have left?"

Add it to your client

The server runs over stdio and is published to npm, so most clients launch it with npx — no global install. Set your key in the PEDRA_API_KEY environment variable inside the config.

{
  "mcpServers": {
    "pedra": {
      "command": "npx",
      "args": ["-y", "@pedra-ai/mcp"],
      "env": { "PEDRA_API_KEY": "your-api-key" }
    }
  }
}

In Claude Desktop, open Settings → Developer → Edit Config and add the pedra entry. In Cursor, use ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Restart the client after saving.

Authentication

The server reads your key from PEDRA_API_KEY. Get one by signing up at app.pedra.ai and opening Settings → API. See Authentication for details.

Tools

One tool per endpoint, all returning final URLs:

• pedra_furnish, pedra_empty_room, pedra_renovation, pedra_edit_via_prompt, pedra_remove_object — see Virtual staging.
• pedra_enhance, pedra_enhance_and_correct_perspective, pedra_sky_blue, pedra_blur — see Image enhancement.
• pedra_create_video, plus pedra_credits and pedra_feedback — see Video and Credits.

Most image tools take an imageUrl — a public URL or a data: URL; some MCP clients also let you attach an image directly. Plus a few optional parameters — your client shows each tool's input schema.

How it works

A thin wrapper over the Pedra Node SDK. Every endpoint blocks and returns the final URL(s) inline — even pedra_create_video, which can take up to ~10 minutes (the API keeps the connection alive with a heartbeat). API errors — insufficient credits, a bad image — come back as readable MCP tool errors, not crashes.

Source & support

The server is MIT-licensed and developed in the open at github.com/pedra-ai/pedra-mcp. Learn more about the protocol at modelcontextprotocol.io, and email felix@pedra.ai for integration help, higher quotas, or enterprise terms.