Catalog Attribute Normalizer vs Xero MCP Server
A side-by-side look at the Catalog Attribute Normalizer and Xero MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Catalog Attribute Normalizer for finance & fintech work over a hosted endpoint; choose Xero MCP Server for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Catalog Attribute Normalizer when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
normalize_catalog.
Choose Xero MCP Server when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
XERO_CLIENT_ID, XERO_CLIENT_SECRET, XERO_SCOPES, XERO_CLIENT_BEARER_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | XERO_CLIENT_IDXERO_CLIENT_SECRETXERO_SCOPESXERO_CLIENT_BEARER_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 385 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Catalog Attribute Normalizer | View Xero MCP Server |
Tools & capabilities
Catalog Attribute Normalizer tools 1
normalize_catalogNormalizes a batch of catalog products (attribute canonicalization/extraction + category-path mapping into the requested target taxonomies: google, shopify, amazon). Returns one result per input product, same order: a NormalizedProduct on success, or { error, source_title } if that specific product's classification failed — one product's failure never voids the rest of the batch. attributes is keyed by a controlled vocabulary (size, color, material, gender, sleeve_length — unrecognized keys are dropped, not passed through under a model-chosen name) and each value carries provenance: "canonicalized" means it came from your own raw_attributes input for that product (deterministic cleanup only, no recall); "extracted" means the model inferred it from the title/description and it wasn't in your input — treat extracted values as a suggestion, not a confirmed fact about the product, the same way you'd treat a low-confidence category_paths entry. category_paths for google and shopify is retrieval-grounded against the real, current taxonomy files (not recalled from memory) — measured at 22/24 (91.7%) exact path+leaf_id matches on a 12-product evaluation set; amazon has no comparable public reference file, so it stays best-effort. Each entry's confidence (0-1) and leaf_id (null when not confident it matches a real node) are the honest signal regardless of taxonomy — treat a low-confidence or null-leaf_id result as a suggestion worth a quick human check, not a confirmed classification.
Xero MCP Server tools
No tool names declared yet. Check the project README from 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.
Catalog Attribute Normalizer
{
"mcpServers": {
"catalog-attribute-normalizer": {
"url": "https://catalog-normalizer.acjlabs.com/mcp"
}
}
}
Xero MCP Server
{
"mcpServers": {
"xeroapi-xero-mcp-server": {
"command": "npx",
"args": [
"-y",
"@xeroapi/xero-mcp-server@latest"
],
"env": {
"XERO_CLIENT_ID": "YOUR_XERO_CLIENT_ID_HERE",
"XERO_CLIENT_SECRET": "YOUR_XERO_CLIENT_SECRET_HERE",
"XERO_SCOPES": "YOUR_XERO_SCOPES_HERE",
"XERO_CLIENT_BEARER_TOKEN": "YOUR_XERO_CLIENT_BEARER_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Catalog Attribute Normalizer is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Xero MCP Server belongs to Finance & Fintech and uses a local stdio subprocess. Pick Catalog Attribute Normalizer for finance & fintech work and Xero MCP Server for finance & fintech.
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.
Catalog Attribute Normalizer has no declared pricing — check the project's own site. Xero MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: oauth 2.0. 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 catalog-attribute-normalizer and xeroapi-xero-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Catalog Attribute Normalizer has a quality signal of 53/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Xero MCP Server has 57/100 (Good) with 3 views, 0 installs and 385 GitHub stars.