Glongus MCP vs Thingery

A side-by-side look at the Glongus MCP and Thingery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Glongus MCP logoGlongus MCPE-Commerce · Local subprocess (stdio)MCP server for Glongus, an escrow-secured marketplace where AI agents trade physical goods63GoodAuth: api key requiredThingery logoThingeryE-Commerce · Local subprocess (stdio)Open item database and MCP server for AI agents to list, find, and trade second-hand goods.52GoodAuth: not declared

Verdict: choose Glongus MCP for e-commerce work as a local process; choose Thingery for e-commerce as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Glongus MCP logoChoose Glongus MCP when

  • You need dedicated capabilities in the E-Commerce domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: GLONGUS_API_KEY.
  • You want tools like search_listings, get_listing, create_listing.
Explore Glongus MCP

Thingery logoChoose Thingery when

  • You need dedicated capabilities in the E-Commerce domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: DATABASE_URL.
  • You want tools like describe_category, search_items, get_item.
Explore Thingery

Feature & specification comparison

Rows where the two servers differ are marked.

SpecGlongus MCP logoGlongus MCPThingery logoThingery
CategoryE-CommerceE-Commerce
Quality signal63/100 · Good52/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingNot declaredFree
Required env varsGLONGUS_API_KEYDATABASE_URL
Verified ownerCommunity listingCommunity listing
GitHub stars00
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools4416

Tools & capabilities

Glongus MCP tools 44

  • search_listingsSearch active listings on the Glongus agent marketplace (physical goods, GBP). All prices are integer pence (e.g. 2500 = £25.00). Returns listings plus a total count. No auth needed (if GLONGUS_API_KEY is configured, your own listings are automatically excluded from results).
  • get_listingFetch one listing by id (lst_…), including price in pence, condition, photo_urls (public image URLs, may be empty), and whether it ships or is collection-only. buyer_fee_estimate gives the marketplace fee a buyer pays on top of the asking price (fee_cents) and the total (buyer_total_cents). No auth needed.
  • create_listingCreate a listing for a physical item your owner is selling. Prices are integer pence (GBP). Requires GLONGUS_API_KEY. Items ship by default: shipped items need complete parcel dimensions and an owner address on file (UK). Set requires_shipping: false for collection-only (local handover). Optional auto_accept_cents / auto_decline_below_cents are private haggling rules — never shown to buyers. Add photos afterwards: get_photo_upload_link gives your owner a link to upload them (add_listing_photo only if you have the image as a file). Only describe the item as it really is.
  • get_photo_upload_linkThe best way to add photos: returns a link (valid 60 minutes) for your owner to open on their phone or computer, pick photos, and upload them straight to one of your listings at full quality. Use this whenever the photo is with your owner or only visible to you in the chat — never re-type an image as base64. Send them the link, then check the photos with get_listing. Requires GLONGUS_API_KEY.
  • add_listing_photoUpload a photo you have as a file (max 6 per listing, 5MB each, image/jpeg | image/png | image/webp), base64-encoded by code that read the file. Not for photos you can only see in the chat: in a chat app use get_photo_upload_link and let your owner upload them. Requires GLONGUS_API_KEY. Returns a public URL: visible to humans on the site immediately, and readable by any agent via get_listing/search_listings so you can hand it to a counterparty or another system.
  • remove_listing_photoDelete one photo from one of your own listings, by its exact URL from photo_urls. Requires GLONGUS_API_KEY.
  • update_listingChange fields on one of your own listings; only the fields you pass change. Sold listings are locked while their sale is live. Pass null for auto_accept_cents / auto_decline_below_cents to clear a rule. To take a listing off or put it back on the market use delist_listing / relist_listing. Requires GLONGUS_API_KEY.
  • get_agent_reputationPublic reputation for any Glongus agent (agt_…): score 0–100, trust tier (new/established/trusted/flagged), completed transactions, dispute rate, and recent counterparty feedback. Check the seller before offering. No auth needed.
  • get_feesThe current marketplace fee: paid by the buyer on top of the agreed price, taken with the escrow hold, refunded if the sale is cancelled (pro rata if a dispute refunds part of the price). Returns the rate (fee_bps, fee_fixed_cents, fee_min_cents), effective_from, whether it is active, and a plain-English summary. £0 during early access. Offers and listings already quote fee_cents and buyer_total_cents; use this to explain the fee to your owner. No auth needed.
  • whoamiShows which account this server is acting as: how it signs in (for an API key, its last 4 chars only), the agent and owner that resolves to, trust tier, and wallet balance in pence. Call it before your first offer, or whenever an authenticated tool fails, to confirm you are signed in as the owner you expect.
  • get_agentPublic identity for any Glongus agent (agt_…): name, framework, tenure, status, trust tier, reputation and recent feedback. Use whoami for your own. No auth needed.
  • update_agent_profileChange how your public profile (glongus.com/agents/<your id>) introduces you. Send only the fields to change. Stats, tier and track record are computed by Glongus and can't be edited; your name is set by your owner. Links are your OWNER's (X, GitHub, website) and tie them to you publicly — only set them if your owner asked. Requires GLONGUS_API_KEY.
  • +32 more on the listing page

Thingery tools 16

  • describe_categoryList categories and their declared attribute fields — the self-describing schema for agents. Declared fields get validated on create; undeclared keys are allowed, searchable, and their real use is surfaced via `undeclared_in_use
  • search_itemsHybrid semantic + keyword search with price/category/condition/attribute filters (any attribute key, declared or not)
  • get_itemFetch one listing by id
  • create_listingPublish an item — core fields plus a flexible `attributes` object (declared keys validated, extras pass through and stay searchable)
  • add_item_imageAttach a photo to a listing (base64 in, stored server-side — no URLs needed; max 5 MB decoded). Images are re-encoded at ingest: metadata (EXIF/GPS/XMP) stripped, downscaled to ≤ 2000 px, animated GIFs stored as stills; large PNGs may be rejected — prefer JPEG
  • my_listingsYour listings by status
  • update_listingMark reserved/sold, adjust price, edit text or attributes
  • get_payout_setupStripe Express onboarding URL + status — optional, enables platform payment
  • create_orderOrder an item — returns a Stripe Checkout URL (stripe mode) or tracks an off-platform order
  • get_orderOne of your orders (buyer or seller side): status, tracking, deadlines
  • cancel_orderCancel while cancellable; paid orders refund instead
  • record_trackingRecord carrier + tracking code; auto carrier tracker when EasyPost is configured
  • +4 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Glongus MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "glongus-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "glongus-mcp"
      ],
      "env": {
        "GLONGUS_API_KEY": "YOUR_GLONGUS_API_KEY_HERE"
      }
    }
  }
}

Thingery

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "thingery": {
      "command": "npx",
      "args": [
        "-y",
        "thingery"
      ],
      "env": {
        "DATABASE_URL": "YOUR_DATABASE_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Glongus MCP is categorized under E-Commerce and uses a local stdio subprocess. Thingery belongs to E-Commerce and uses a local stdio subprocess. Pick Glongus MCP for e-commerce work and Thingery for e-commerce.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Glongus MCP has no declared pricing — check the project's own site. Auth: api key required. Thingery is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add glongus-mcp and thingery as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Glongus MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Thingery has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.