Server Everything vs Thingery
A side-by-side look at the Server Everything and Thingery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Server Everything for other tools and integrations 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?
Choose Server Everything when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | E-Commerce |
| Quality signal | 55/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Free |
| Required env vars | None listed | DATABASE_URL |
| Verified owner | Community listing | Community listing |
| GitHub stars | 91,405 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 16 |
| Full listing | View Server Everything | View Thingery |
Tools & capabilities
Server Everything tools
No tool names declared yet. Check the project README from 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_usesearch_itemsHybrid semantic + keyword search with price/category/condition/attribute filters (any attribute key, declared or not)get_itemFetch one listing by idcreate_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 JPEGmy_listingsYour listings by statusupdate_listingMark reserved/sold, adjust price, edit text or attributesget_payout_setupStripe Express onboarding URL + status — optional, enables platform paymentcreate_orderOrder an item — returns a Stripe Checkout URL (stripe mode) or tracks an off-platform orderget_orderOne of your orders (buyer or seller side): status, tracking, deadlinescancel_orderCancel while cancellable; paid orders refund insteadrecord_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.
Server Everything
{
"mcpServers": {
"modelcontextprotocol-server-everything": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-everything"
]
}
}
}
Thingery
{
"mcpServers": {
"thingery": {
"command": "npx",
"args": [
"-y",
"thingery"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE"
}
}
}
}
Frequently asked questions
Server Everything is categorized under Other Tools and Integrations and uses a local stdio subprocess. Thingery belongs to E-Commerce and uses a local stdio subprocess. Pick Server Everything for other tools and integrations 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.
Server Everything is listed as free. Auth: no auth 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 modelcontextprotocol-server-everything and thingery as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Server Everything has a quality signal of 55/100 (Good) with 9 views, 0 installs and 91,405 GitHub stars. Thingery has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.