Pebbler Human Feedback
LocalAbout Pebbler Human Feedback
Pebbler Human Feedback lets an agent run image A/B preference tests with participants on the Pebbler app. The connector retrieves current offers, prepares and purchases tests within locally configured USDC limits, and returns progress and aggregate results.
Key features
- 01Discover current packages and availability
- 02Create image preference test drafts
- 03Refresh quotes before payment
- 04Purchase within configured USDC limits
- 05Check progress and aggregate vote shares
Use cases
- 01Compare two image concepts with human votes
- 02Review a live quote before purchasing a test
- 03Check partial results while responses arrive
- 04Return to saved studies after a restart
MCP support
Exposes tools for catalog discovery, image study creation, quote refresh, purchase, status, results and local study listing. Payments are disabled unless enabled explicitly; wallet credentials and spending limits are configured locally.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @pebbler/pebbler-mcpPEBBLER_ALLOW_PAYMENTSExplicitly enable local wallet signingPEBBLER_WALLET_PRIVATE_KEYSecretLocal wallet signing key; required only for paymentsPEBBLER_MAX_PURCHASE_USDCYour maximum USDC spend per test. Required when payments are enabled.PEBBLER_MAX_TOTAL_USDCYour cumulative USDC spending limit. Required when payments are enabled; does not reset automatically.PEBBLER_STATE_DIROptional private folder to retain access to your tests across restarts.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
7Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMEPebbler MCP
Let your agent collect human feedback on two images and explain the results. Pebbler runs image preference tests with participants on the Pebbler app.
Your agent retrieves current pricing, package details and availability before creating a test. The purchase uses a live quote and stays within the spending limits you configure. Pricing and package sizes are not fixed by this connector.
Version 1 supports image A/B preference tests. These measure which image people prefer, rather than product conversion or causal effects. Completed response counts are not guaranteed. Surveys and text-only comparisons are not supported.
Connect your agent
Use an MCP app that supports local servers and Node.js 22 or later. Add this configuration to your app:
{
"mcpServers": {
"pebbler": {
"command": "npx",
"args": ["-y", "@pebbler/[email protected]"]
}
}
}
Pebbler's production settings are included. You can explore current packages and create drafts without enabling payments.
Enable purchases
Use a dedicated wallet funded with native USDC on Base. Configure these settings locally in your MCP app's environment or secret settings:
| Setting | What to provide |
|---|---|
PEBBLER_ALLOW_PAYMENTS | Set to true when you want the agent to make purchases |
PEBBLER_WALLET_PRIVATE_KEY | Your wallet's signing key, supplied privately |
PEBBLER_MAX_PURCHASE_USDC | Your chosen maximum spend per test, as a positive decimal USDC amount |
PEBBLER_MAX_TOTAL_USDC | Your chosen cumulative spending limit, as a positive decimal USDC amount |
Both spending limits are required when payments are enabled. They are your budget, not the price of a test. If a quote exceeds either limit, the connector stops instead of raising your budget. Payments stay disabled until you enable them explicitly.
The wallet key remains local. Do not put it in a prompt or share it in a conversation. Prices and quotes are fetched by the agent; you do not need to configure them.
Ask for a test
For example:
Check the current package and price, then compare these two image URLs. Tell me the quote before buying and stay within my configured budget.
Provide two publicly accessible HTTPS image URLs and a clear question. Use images you own or have permission to use, and keep the URLs available while responses are collected.
Your agent can show the current offer, create a draft, purchase the test and check progress. You can read partial results while collection continues or return later to ask for the final counts and vote shares. Retrieving results is included in the purchase.
Available tools
| Tool | Purpose |
|---|---|
get_catalog | Retrieve current packages, prices, supported inputs and availability |
create_study | Prepare an image comparison and obtain its quote |
quote_study | Refresh a quote before payment has been signed |
purchase_study | Purchase the quoted test within your wallet's spending limits |
get_study_status | Check progress and when to check again |
get_study_results | Retrieve aggregate A/B votes and shares |
list_local_studies | Find your saved tests after returning or restarting |
The agent learns each tool's inputs automatically when connected. It should read the catalog first, use the quote for the purchase, and follow the returned polling interval when checking progress.
Returning to your results
Keep the connector's private local state folder backed up. It retains access to your tests and their purchase history across restarts. You can choose a folder with PEBBLER_STATE_DIR; use the same folder when returning to existing tests.
Your total spending limit counts retained signed purchases, including unresolved attempts, and does not reset automatically. Increase it deliberately if you want to buy more tests. Keep the original state rather than deleting it to reset your budget.
If a purchase is interrupted or pending, ask the agent to retry that same purchase. The connector preserves its identifiers and payment authorization instead of signing another payment. Reading progress and results does not require another purchase.
Try an example
The included examples/run-study.mjs demonstrates discovery and creating an image comparison. It prints the live catalog and quote; purchasing requires the --purchase flag and your locally configured wallet and budgets.
License
MIT. Original example image assets are included under the same license.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.