Placid.app MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Placid.app MCP Server?

Placid.app MCP Server is an implementation designed to integrate with the Placid.app API, allowing users to list templates and generate creatives through the Model Context Protocol.

How to use Placid.app MCP Server?

To use the MCP Server, you can install it via Smithery or NPX, and then configure it with your Placid API token to start generating creatives.

Key features of Placid.app MCP Server?

  • List available Placid templates with filtering options
  • Generate creatives using templates and dynamic content
  • Secure API token management
  • Error handling and validation
  • Type-safe implementation

Use cases of Placid.app MCP Server?

  1. Automating the generation of marketing creatives
  2. Integrating with applications that require dynamic content generation
  3. Streamlining the process of template management for design teams

FAQ from Placid.app MCP Server?

  • How do I get my Placid API token?

Log in to your Placid.app account, go to Settings > API, and create a new API token.

  • Can I filter templates when listing them?

Yes! You can filter templates by collection ID, custom data, and tags.

  • Is there a manual installation option?

Yes, you can clone the repository and install dependencies manually.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 minutes ago