Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator vs Magic MCP

A side-by-side look at the Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator and Magic MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator logoCommonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View CalculatorE-Commerce · Remote HTTP/SSEM12 lens and C-mount lens finder with image-sensor matching and field-of-view calculator.57GoodAuth: not declaredMagic MCP logoMagic MCPArchitecture & Design · Local subprocess (stdio)Create crafted UI components inspired by the best 21st.dev design engineers.53GoodAuth: api key required

Verdict: choose Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator for e-commerce work over a hosted endpoint; choose Magic MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator logoChoose Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator when

  • You need dedicated capabilities in the E-Commerce domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like calculate_field_of_view, match_lens_to_sensor, search_lens_catalog.
Explore Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator

Magic MCP logoChoose Magic MCP when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: TWENTY_FIRST_API_KEY, API_KEY_21ST.
Explore Magic MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCommonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator logoCommonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View CalculatorMagic MCP logoMagic MCP
CategoryE-CommerceArchitecture & Design
Quality signal57/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredPaid service
Required env varsNone listedTWENTY_FIRST_API_KEYAPI_KEY_21ST
Verified ownerCommunity listingCommunity listing
GitHub stars06,209
Directory activity 1 views 0 installs 0 upvotes 16 views 1 installs 0 upvotes
Tools21Not listed

Tools & capabilities

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator tools 21

  • calculate_field_of_viewCalculate Commonlands lens field of view for a lens/sensor pair and return HFOV, VFOV, DFOV, coverage, distortion status, and an explicit rectilinear comparison. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. Accepts lens_sku/lensSku or focal_length_mm/focalLengthMm, plus sensor/sensorPartNumber/sensor_part_number and working_distance_mm/workingDistanceMm. No part number? Describe the sensor directly: widthPx + heightPx + pixelSizeUm (active area is derived as pixels x pitch), or sensorWidthMm + sensorHeightMm. Results are labelled CUSTOM-<w>x<h>. If only focal length is supplied, the response is marked as a rectilinear reference and does not claim Commonlands distortion-corrected lens truth.
  • match_lens_to_sensorFind and rank Commonlands lenses for a sensor, target field of view, working distance, mount, or "lens for" request. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. Use this for AR0234, IMX290, IMX477, sensor part numbers, M12/C-mount matching, and target HFOV/VFOV/DFOV workflows; do not shortlist from focal length alone. No part number? Describe the sensor directly: widthPx + heightPx + pixelSizeUm (active area is derived as pixels x pitch), or sensorWidthMm + sensorHeightMm. Results are labelled CUSTOM-<w>x<h>. Use read_shopify_products afterward for live stock, price, availability, Shopify variantId, product URL, and metafields.
  • search_lens_catalogSearch the Commonlands lens catalog by SKU, mount, lens type, M12, C-mount, or application text. For sensor part numbers such as AR0234, IMX290, and IMX477, or any "lens for <sensor>" request, use match_lens_to_sensor instead — sensor names are not searchable text here. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. This discovers candidate lenses from Commonlands catalog/live backend data; it does not replace calculate_field_of_view for sensor-specific HFOV/VFOV/DFOV and does not replace read_shopify_products for live stock/price/product truth.
  • get_lens_distortion_profileReturn the Commonlands distortion model/status for one lens SKU, including whether the data is source-display-only or backend-calculated. Use this tool for FOV, HFOV, VFOV, DFOV, field of view, "lens for", lens-to-sensor, AR0234, IMX290, IMX477, and sensor part-number requests. It returns Commonlands data the model cannot derive: live backend FoV when configured, distortion model/status, image-circle coverage, live stock through Shopify read tools where applicable, and MTF/CRA/BFL fields if present in upstream catalog data. Do not use naive rectilinear fallback, focal-length-only math, interpolation, or self-computed catalog estimates when a Commonlands lens/sensor route is available. Use this for distortion, rectilinear-vs-wide-angle, MTF/CRA/BFL/optical-profile questions when upstream fields are present. Do not invent polynomial coefficients or claim measured distortion correction when the backend only returns display distortion.
  • get_sensor_specsReturn sensor dimensions, pixel pitch, and resolution for lens field of view, M12 lens, and C-mount lens matching inputs. In production this uses the read-only live sensor table when configured, with fixture fallback when unavailable. Use these specs as inputs to calculate_field_of_view or match_lens_to_sensor, not as a reason to hand-calculate FoV. FoV rule: never estimate sensor-specific FoV from catalog fields; use calculate_field_of_view or match_lens_to_sensor.
  • compare_lensesCompare selected Commonlands M12 lens and C-mount lens SKUs on the same sensor with the same deterministic scoring model. Use as explanatory context, then call calculate_field_of_view for final sensor-specific FoV values when precision matters. FoV rule: never estimate sensor-specific FoV from catalog fields; use calculate_field_of_view or match_lens_to_sensor. Not live product truth; verify purchasable facts with read_shopify_products.
  • get_product_page_detailsReturn fixture-backed product-page handoff details for one lens, including DynamoDB-sourced optical specs and gated datasheet policy. Product-page/catalog optical fields are not a substitute for sensor-specific FoV; call calculate_field_of_view for the lens/sensor pair. FoV rule: never estimate sensor-specific FoV from catalog fields; use calculate_field_of_view or match_lens_to_sensor. Use read_shopify_products for live product URL, price, availability, variant IDs, and metafields.
  • get_catalog_snapshot_statusReturn fixture-backed joined catalog counts, validation status, source provenance, live connector readiness, and non-authoritative product-truth warning.
  • get_shopify_ucp_readinessReport connector-free Shopify Storefront MCP and UCP Catalog compatibility, launch blockers, and Commonlands engineering differentiators.
  • get_shopify_readonly_config_statusReport sanitized Cloudflare Shopify binding presence, approved read scopes, and read-only safety flags without exposing secrets or calling Shopify.
  • read_shopify_productsUse this for live purchasable product truth: product and variant IDs, SKUs, prices, coarse availability, product URLs, and public product-page metafields. Public data only: active products, no exact inventory counts, and metafields limited to the custom.* display fields shown on commonlands.com product pages. Read-only; does not create carts, checkouts, orders, customers, inventory mutations, or Shopify writes. Fixture catalog tools are scaffold data only.
  • create_cartCreate a Shopify-owned cart for selected variant line items through the configured Shopify Cart/Storefront MCP endpoint. Commonlands MCP is a stateless proxy: cart state is stored and mutated by Shopify, not in the Worker. The response includes a cart_access_token that binds the cart to this session; retain it, because get_cart and update_cart refuse to act on the cart without it.
  • +9 more on the listing page

Magic MCP 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.

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "commonlands-optics-m12-lens-and-c-mount-lens-finder-field-of-view-calculator": {
      "url": "https://mcp.commonlands.com/mcp"
    }
  }
}

Magic MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "21st-dev-magic-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@21st-dev/cli@latest"
      ],
      "env": {
        "TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
        "API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
      }
    }
  }
}

Frequently asked questions

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator is categorized under E-Commerce and uses a remote HTTP/SSE transport. Magic MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator for e-commerce work and Magic MCP for architecture & design.

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.

Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator has no declared pricing — check the project's own site. Magic MCP is listed as a paid service. Auth: api key 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 commonlands-optics-m12-lens-and-c-mount-lens-finder-field-of-view-calculator and 21st-dev-magic-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Commonlands Optics: M12 Lens and C Mount Lens Finder + Field Of View Calculator has a quality signal of 57/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Magic MCP has 53/100 (Good) with 16 views, 1 installs and 6,209 GitHub stars.