Sharetribe MCP. Manage listings, transactions, and users programmatically.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Sharetribe MCP Server gives your AI agent full administrative control over a custom marketplace. You can manage listings, audit user profiles, and force payment transitions using natural language prompts.
It lets your client perform operations—like approving entries or marking transactions as complete—without navigating complex vendor panels.
What your AI agents can do
Approve listing
Marks a pending listing as approved, making it publicly visible on the marketplace.
Get listing
Pulls all specific details for one single marketplace entry using its unique ID.
Get transaction
Retrieves deep details and current status for a specific payment or booking transaction.
The agent lists all marketplace entries, retrieves specific listing details, and approves pending items for public visibility.
You can read the status of any transaction and advance its lifecycle—moving an order from 'pending' to 'confirmed' or 'complete'.
The agent fetches user profiles and lists all registered users, allowing you to check account details or track behavior.
You can pull a complete list of marketplace reviews for moderation, checking both positive feedback and problematic content.
The client lists all transactions and listings in the system, giving you an overview of what's happening across the platform.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Sharetribe MCP Server: 9 Tools for Ops Management
These nine tools let your agent perform administrative actions—from listing moderation to transaction state changes—on a custom marketplace.
019d7606approve listing
Marks a pending listing as approved, making it publicly visible on the marketplace.
019d7606get listing
Pulls all specific details for one single marketplace entry using its unique ID.
019d7606get transaction
Retrieves deep details and current status for a specific payment or booking transaction.
019d7606get user
Gets the full profile and account data for a single registered user.
019d7606list listings
Generates an enumerated list of all marketplace listings, often filtered by status or category.
019d7606list reviews
Pulls a collection of reviews left on the platform for moderation and auditing.
019d7606list transactions
Provides an overview list of all historical and current marketplace financial transactions.
019d7606list users
Lists every user account registered on the platform, providing a directory for audits.
019d7606transition transaction
Forces an existing transaction to move from its current state (like 'pending') to a new operational state (like 'complete').
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Sharetribe, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
This server gives your AI agent full admin control over a custom marketplace, letting you manage listings, audit user profiles, and force payment transitions using nothing but natural language prompts. You don't have to navigate complex vendor panels; your agent just talks to the system and gets it done.
Moderate Listings: To get an overview of every piece of inventory, your agent runs list_listings, which generates a full directory of all marketplace entries, often filtered by status or category. If you need the granular details for one specific item—say, checking dimensions or vendor notes—you pull those exact specifics using get_listing with its unique ID.
Once you've vetted an entry and it’s ready to go live, your agent approves it instantly with approve_listing, making it publicly visible on the marketplace.
Track Market Activity: To keep tabs on what’s actually happening financially across the platform, your client uses list_transactions for a broad overview of all historical and current financial movements. If you need deep visibility into one particular payment or booking—maybe checking why a deposit stalled—you call get_transaction, which retrieves every detail and the exact status of that single record.
When an order is ready to move from 'pending' to 'complete,' your agent forces operational momentum using transition_transaction. This action moves an existing transaction to a new state, closing out the lifecycle.
Audit User Profiles: You gotta keep tabs on who’s doing what. To see every person registered in the system, your agent runs list_users, giving you a complete directory for audits. If you want to check someone's account history or profile details—maybe verify their address or membership status—your agent calls get_user with that individual's specific data.
For behavioral tracking and moderation, it pulls a full collection of reviews using list_reviews, letting you audit everything from glowing feedback to problematic content.
The Full Scope: Your AI client handles three core areas: the goods (listings), the people (users), and the money (transactions). You get administrative power over listing visibility by running list_listings and then approving items with approve_listing. If you need to verify a transaction’s status, it'll pull all records via list_transactions, check specific details using get_transaction, or force the state change with transition_transaction.
Similarly, when auditing people, your agent lists every account using list_users and gets deep profile info for any single user. You can also keep an eye on the whole marketplace activity by calling list_reviews to check all moderation queues.
How Sharetribe MCP Works
- 1 Tell your AI agent which data set to look at (e.g., 'list all pending listings').
- 2 The server returns a list or record ID, and you specify the target item.
- 3 Your agent runs the appropriate tool (like
approve_listing) using the provided IDs to execute the desired action.
The bottom line is: You talk to your agent like it's an admin user on the platform's backend, and it executes the necessary function calls automatically.
Who Is Sharetribe MCP For?
Platform Operations Managers or Product Owners who spend too much time clicking through dashboards. If you constantly have to manually approve entries, force payment states, or audit user accounts via a UI, this is for you. You're tired of the admin panel and need direct API control.
Handles daily flow issues: identifying stalled transactions using list_transactions or forcing an order state forward with transition_transaction.
Manages the entire site's content lifecycle, running checks like list_listings to find items stuck in 'pendingApproval' status.
Keeps the community clean by running list_reviews and auditing user behavior using get_user when problematic activity is flagged.
What Changes When You Connect
- Speed up content moderation. Instead of clicking through pages to find items needing review, you ask your agent to run
list_listingsand then usesapprove_listingon the results instantly. No UI friction. - Solve payment bottlenecks. When a transaction stalls in limbo, don't wait for manual intervention. You can audit it with
get_transactionand force progress usingtransition_transaction—you get immediate state change confirmation. - Maintain data integrity. By running
list_users, you can pull account lists to check compliance or identify inactive accounts before they become a problem. It's full visibility, zero clicks. - Automate audit logging. You don't need multiple tabs open for user checks. Running
get_usergives you the specific profile data needed—whether it's for a suspicious account or just verifying details. - Centralize oversight. Instead of checking transaction logs in one place and reviews in another, your agent uses
list_transactionsandlist_reviewsto pull all operational concerns into one chat thread.
Real-World Use Cases
A listing got stuck in 'pendingApproval'.
An admin finds a handful of new listings that never get approved. Instead of manually filtering by status, they tell their agent to run list_listings and filter strictly for the 'pendingApproval' state index. The agent pulls the IDs, then uses get_listing on each ID to review it before running approve_listing. Problem solved in minutes.
A customer reported a payment failure.
The support team gets notified about an order stuck at 'preauthorized.' They tell their agent to run get_transaction using the order ID. The agent confirms the status and, if necessary, runs transition_transaction to move it past the payment hurdle. This fixes the issue without touching a dashboard.
A user is repeatedly posting bad content.
The moderator needs to review the account history for a banned user. They start by running list_users to find the ID, then use get_user to see the full profile details and behavior patterns. Finally, they run list_reviews to pull all associated negative feedback.
Running an end-of-day financial reconciliation.
The finance team needs a snapshot of all completed sales. They instruct their agent to run list_transactions, filtering for 'complete' status, giving them the total count and IDs needed to generate reports. This is much faster than running reports in a separate accounting tool.
The Tradeoffs
Confusing read vs write tools
Thinking that calling get_listing gives you the ability to approve an item. It just pulls data; it won't change anything.
→
To view details, use get_listing. To actually mark it as approved and make it live, you must call approve_listing. They do two different things.
Assuming state changes happen automatically
Waiting for a payment to 'complete' just because the customer paid. The system needs an explicit command.
→
If a transaction is ready to move forward, you can't wait around. You have to tell your agent to run transition_transaction and specify the target state.
Trying to audit without context
Just running list_users and getting a giant list of 10,000 accounts. You don't know who is bad.
→
First, run list_reviews to identify the problematic IDs or account names. Then, use those specific IDs with get_user to get context on why they are flagged.
When It Fits, When It Doesn't
Use this Sharetribe MCP Server if your primary bottleneck is manual oversight: approving content, changing payment states, or auditing user behavior across a custom marketplace. It's designed for the 'operations layer.'
Don't use it if you only need to read simple data—if all you ever do is pull one single listing detail by ID, then just using get_listing might suffice. However, since this server gives access to nine tools, you are always better off connecting it. It covers everything from basic reads (list_listings) to complex writes (transition_transaction).
If your workflow involves multiple sequential steps—like 'Find pending listings' -> get_listing on each one -> then decide if they need approval and run approve_listing—this is the right tool. It handles that full, multi-step process in a single chat session.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Sharetribe. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 9 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Handling marketplace content moderation shouldn't require jumping between three different dashboards.
Today, if a user submits a listing that needs review, you open the vendor portal to check basic info. Then, you switch tabs to the payments dashboard to see if they paid deposits, and finally, you jump to the reviews page to look for complaints. It’s three separate logins just to greenlight one entry.
With the Sharetribe MCP Server, your agent handles the whole flow in a conversation. You prompt it to check all pending listings. The agent runs `list_listings`, pulls details with `get_listing` on the results, and if they pass muster, it executes `approve_listing`. Done.
Sharetribe MCP Server: Get payment status and force transitions.
Manual workflows often get stuck because a transaction moves from 'paid' to 'pending fulfillment,' but no one clicks the final button. You spend time emailing accounting or waiting for someone to remember to update the state on the dashboard, only to find out it was just an API oversight.
The `transition_transaction` tool eliminates that wait time. Your agent can read the status using `get_transaction`, identify the blockage, and execute the required transition immediately. It moves the money flow without needing a human in the loop.
Common Questions About Sharetribe MCP
How do I find all listings that are waiting for review using list_listings? +
You can run list_listings and filter by the specific status ID, like 'pendingApproval.' This function returns a collection of IDs for every item in that state. You then use get_listing on those IDs to see the content.
Can I force an order from pending to complete using transition_transaction? +
Yes, that's what transition_transaction does. You must first provide the specific transaction ID and then tell the agent the target state (e.g., 'complete'). The tool moves it and confirms the change.
What is the difference between get_listing and list_listings? +
list_listings gives you a directory—a collection of IDs or summaries for many listings. get_listing, however, takes one specific ID and returns all the deep details on just that single entry.
How do I check if a user is authorized to approve something? +
You should run list_users first to get an overview. If you need deeper context on their behavior, use get_user. This helps verify the account's status before running tools like approve_listing.
If I run `get_listing` with an invalid ID, what error does my agent receive? +
It returns a specific HTTP 404 status code and an empty data payload. Your AI client must check for this explicit failure state to prevent the workflow from halting unexpectedly.
Does running `list_users` repeatedly cause rate limiting issues? +
Yes, continuous calls to list functions consume your API quota rapidly. We suggest batching requests or adding a small delay loop between multiple data pulls for stable performance.
When I use `list_transactions`, what core metrics are guaranteed in the output? +
The result set always includes the transaction UUID, its current status code, and the associated user ID. This reliable structure lets your agent immediately verify order ownership and lifecycle stage.
How do I filter `list_reviews` to only see reviews for a specific listing? +
You must pass the target listing's unique ID as a mandatory parameter in the call. This limits the scope, ensuring your agent analyzes only the reviews tied directly to that piece of inventory.
Can the AI forcefully complete an active marketplace payment transition? +
Absolutely. Through the transition_transaction method, your prompt can dictate the order pipeline. Ensure you pass the specific UUID of the order and the explicit, configured transition name (e.g., "transition/accept" or "transition/complete") to force the lifecycle into its subsequent operational phase immediately.
Why use the Integration API instead of the Marketplace API? +
Because the Integration API is the unadulterated administrator backend designed for secure backend logic rather than client interfaces. This permits system-level moderation, transaction configuration, and override state.
Can this integration modify review ratings directly? +
Currently, the integration specifically implements list_reviews as a query mechanism tailored exclusively around monitoring and auditing capabilities. It does not actively expose a write mutation structurally to alter or destroy existing community integrity ratings.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
PushEngage
Re-engage website visitors with browser push notifications that increase traffic, recover abandoned carts, and boost retention.
Weimob / 微盟
Leading E-commerce and marketing SaaS platform in China — manage products, orders, and members via AI.
Best Buy
Search products, check store availability, read reviews, and explore categories via Best Buy — execute retail inquiries directly from any AI agent.
You might also like
Clerk
Add production-ready authentication to your app with user management, SSO, multi-factor auth, and session handling out of the box.
Goodcall
Answer business phone calls with an AI receptionist that schedules appointments, takes messages, and never puts callers on hold.
Eden AI
Equip your AI agent to manage unified AI workflows, track providers, and monitor API usage via the Eden AI platform.