Thingery vs Codebase Memory MCP
A side-by-side look at the Thingery and Codebase Memory MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Thingery for e-commerce work as a local process; choose Codebase Memory MCP for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Codebase Memory MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
index_repository, search_graph, query_graph.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | Knowledge & Memory |
| Quality signal | 52/100 · Good | 73/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | DATABASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 47,004 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 1 installs 1 upvotes |
| Tools | 16 | 17 |
| Full listing | View Thingery | View Codebase Memory MCP |
Tools & capabilities
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
Codebase Memory MCP tools 17
index_repositoryIndex a repository. full/moderate add semantics; fast omits them; cross-repo-intelligence links services. Reports coverage gaps.search_graphFind symbols via BM25 query, regex name/qn filters, or semantic_query. Rows keep qn/file/lines and in/out over CALLS/USAGE/CALL_REFERENCE/INHERITS/IMPLEMENTS.query_graphRead-only Cypher for multi-hop, aggregation, complexity, or cross-service analysis. Default: 200 visible rows with exact/lower-bound totals and truncation; continue safely with next_cursor. graph=missed is a file tree of flagged coverage gaps; absence is not proof of completeness. Use get_graph_schema(diagnostics=full) for properties.trace_pathTrace callers/callees, data flow, or cross-service paths. Defaults exclude tests and resolver evidence. Rows keep qn/hop with explicit totals, relations, and continuations.get_code_snippetRead a search_graph symbol. auto bounds source and outlines large containers; full restores up to 500 lines. Source/outline pages continue; coverage_note marks gaps.get_file_outlineDeclaration outline of one exact repository-relative file: optional exact label filter, source order, exact total/offset/limit paging; file/folder/container nodes excluded.get_graph_schemaGet node-label and edge-type counts. diagnostics=full also lists queryable properties.compare_graphsCompare two indexed snapshots: deterministic target-only additions and base-only removals of stable node/edge identities; each set capped by limit and a 512 KiB budget with exact totals and truncation reasons.get_architectureCompact counts, languages, packages, entry points. Request structure, dependencies, routes, hotspots, boundaries, layers, clusters, cycles, or file_tree; path scopes a directory.search_codeGraph-ranked text search: compact symbols, full bounded source, or file paths.list_projectsList projects with stable paging. Identity is lean; stats adds graph sizes.delete_projectDelete a project from the index- +5 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.
Thingery
{
"mcpServers": {
"thingery": {
"command": "npx",
"args": [
"-y",
"thingery"
],
"env": {
"DATABASE_URL": "YOUR_DATABASE_URL_HERE"
}
}
}
}
Codebase Memory MCP
{
"mcpServers": {
"deusdata-codebase-memory-mcp": {
"command": "npx",
"args": [
"-y",
"codebase-memory-mcp"
]
}
}
}
Frequently asked questions
Thingery is categorized under E-Commerce and uses a local stdio subprocess. Codebase Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Thingery for e-commerce work and Codebase Memory MCP for knowledge & memory.
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.
Thingery is listed as free. Codebase Memory MCP is listed as free. Auth: no auth required. 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 thingery and deusdata-codebase-memory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Thingery has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Codebase Memory MCP has 73/100 (Great) with 8 views, 1 installs and 47,004 GitHub stars.