Delora MCP vs Primitiv — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Delora MCP vs Primitiv
In-depth architectural comparison of the Delora MCP and Primitiv MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Delora MCP
Finance & Fintech · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Primitiv
Finance & Fintech · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Delora MCP if you need specialized Finance & Fintech tools running via a hosted cloud SSE transport. Choose Primitiv if your workspace requires Finance & Fintech integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
D
Choose Delora MCP when:
You need dedicated capabilities in the Finance & Fintech domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Delora MCP server for cross-chain quotes, supported chains, tokens, and tools.
Design contract layer for your codebase. Scans Figma, code, Storybook, and token files, reconciles conflicts, and serves a single machine-readable source of truth over MCP so every agent gets the same authoritative design rules before it builds. Local-first — your code never leaves your machine.
Delora MCP is categorized under Finance & Fintech and uses a remote streaming HTTP/SSE transport. In contrast, Primitiv belongs to Finance & Fintech using local stdio subprocess. Select Delora MCP when you need capabilities focused on finance & fintech and Primitiv when you require tools for finance & fintech.
Get tokens, components, conflicts, inferred rules, and violation count. Default (no category) returns a summary with counts. Pass `category: "all" \
get_token
Look up a specific token by name. Pass `category` to narrow search (e.g. `"colors"`, `"spacing"`, `"borderRadius"`); aliases like `"radius"` / `"z-index"` are normalized.
get_component
Look up a specific component by name. Returns props, variants, source provenance, and `kind` — `component`, `screen`, `provider`, `icon`, or `other`, so agents reuse real UI and skip screens/providers/icons.
get_conflicts
Get conflicts between sources. Pass `type: "all" \
get_inferred_rules
Get the design rules Primitiv has extracted from your codebase patterns. Pass `category` to filter.
get_violations
List token-misuse violations — hardcoded literals in source that bypass the contract, with a suggested token when one fits. Pass `category: "all" \