Skip to main content
Glama
685,691 tools. Updated 2026-10-21 13:47

"Plurk" matching MCP tools:

  • Create new Plurk posts with secure authentication while automatically enforcing daily posting limits to maintain controlled social media activity.
    MIT
  • Post replies to Plurk threads using the plurk-mcp server. Reply to owned threads or explicit mentions with provided credentials and content.
    MIT
  • Retrieve the authenticated Plurk user profile using provided API credentials to access account information and context.
    MIT
  • Update a contact's email address or custom fields, modifying only the fields you supply. Use to correct an address or set custom data; not for subscription changes.
    MIT
  • Score an engram's statement, domain, and tags against scope covers to suggest matching registered scopes. Returns ranked candidates; advisory only.
    Apache 2.0

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    A secure Model Context Protocol server for interacting with Plurk, allowing agents to read account context, post updates, and manage replies. It includes built-in safety guardrails such as daily post limits and reply cooldowns to ensure controlled execution.
    6
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    A Model Context Protocol server for Plunk, the open-source self-hosted email platform. Provides 84 tools for transactional email, contacts, campaigns, segments, templates, workflows, events, and analytics through the Plunk API.
    94
    8 npm
    2
    MIT
  • Record a contact event to drive workflow triggers and segment filters. Auto-creates the contact if missing; omit subscribed to keep opt-out state.
    MIT
  • Persist multiple engrams in a single batch call, applying sequential deduplication and isolating per-item failures, so bulk knowledge storage takes one request instead of many.
    Apache 2.0
  • Search stored engrams by BM25 keyword matching to retrieve relevant agent memory entries.
    Apache 2.0
  • Send a one-off transactional email to specific recipients using subject and body or a template, ideal for receipts, replies, and notifications.
    MIT
    Destructive
  • Permanently delete a contact and their event history in Plunk for genuine erasure requests. Confirms deletion; use unsubscribe instead to stop mail without losing opt-out records.
    MIT
    Destructive
  • Permanently erase up to 1,000 contacts along with their event histories in one call. Use for true data erasure; returns a job id to poll for status.
    MIT
    Destructive
  • Delete a custom contact field and all its stored values from every contact in Plunk when the field is no longer needed. Confirm field usage first, since segments filtering on it will stop matching.
    MIT
    Destructive
  • Archive a Plunk campaign to hide it from the default list while keeping its performance history intact. Use instead of deleting to preserve records of finished or abandoned campaigns.
    MIT
  • List saved audience segments with names, types, sizes, and IDs to find the right segment for a campaign or see which audiences exist and their sizes.
    MIT
  • List every reusable email template with its ID, name, and subject, so you can find a template ID for sends, campaigns, or workflow steps.
    MIT
  • Copy a workflow with all its steps and transitions into a new disabled version, so you can rework an automation without disturbing the one currently running.
    MIT
  • Remove a step from a workflow. After deletion, transitions are left dangling; fetch the workflow and reconnect the graph to avoid contact stalls.
    MIT
    Destructive