Pincushion for Openclaw

1. Register the MCP Server

Run the following command to append the Pincushion server details to your local configuration. Be sure to replace /path/to/your/project with your absolute repository path:

openclaw mcp add pincushion \
  --command npx \
  --arg -y \
  --arg pincushion-mcp \
  --arg --project-dir \
  --arg /path/to/your/project \
  --arg --cloud-sync

Reload the agent context to register the newly available tools provided by these Openclaw Skills:

openclaw mcp reload && openclaw mcp list

2. Authenticate for Cloud Sync

To allow stakeholders to submit pins from deployed or staging environments to a headless agent, obtain a license key from pincushion.io. Write this key directly to your project root to avoid environment-filtering issues with MCP runtimes:

echo "YOUR_LICENSE_KEY" > /path/to/your/project/.feedback/.license-key

3. Embed the Widget

Include this script in your application's root layout or HTML template to let users drop pins without requiring any browser extensions:

<script src="https://pincushion.io/widget/pin.js" data-project="YOUR_PROJECT_ID" defer></script>

Pincushion coordinates feedback data either locally or via cloud synchronization. When using this toolset alongside Openclaw Skills, the workspace data is organized as follows:

File Structure

Work Packet Metadata Taxonomy

Each pin contains programmatic context structures designed for ingestion by coding agents:

• CSS Selector: The precise element target identifier in the DOM.
• DOM Snippet: Associated HTML segment representing the state of the target area.
• Viewport details: Screen size and dimensions where the issue was observed.
• Screenshots: High-fidelity visual assets displaying the rendered interface.
• Comment Thread: Historical discussion context and stakeholder requirements.