iDevice Wearables

Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura.

CommunityDegradedAPI key requiredGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    An API key from the service settings is required

    Wearable tech roadmaps: Apple, Meta, Samsung, Google, Oura. Claims, timelines, analysis.

    How to connect

    How to connect iDevice Wearables to Claude

    The server address to paste into Claude settings:

    https://idevice.com/api/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect iDevice Wearables to ChatGPT

    The server address to paste into ChatGPT settings:

    https://idevice.com/api/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect iDevice Wearables to Cursor

    The server address to paste into Cursor settings:

    https://idevice.com/api/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (6)

    Raw names from tools/list. Only developers need these.

    list_productsEvery product iDevice tracks, with its lifecycle (rumored, announced, preorder, shipping, previous) and how many well-sourced claims it has (can be 0). Use this first to find the product_slug for the other tools. Optional query filters by name, e.g. 'iphone 18 pro'.
    get_productLifecycle, official or estimated price, key dates, claim count and how well-sourced the claims are. Works for products with no claims yet.
    get_product_factsOfficial price (only when the maker announced or is selling it; otherwise labelled as an estimate), announcement and availability dates with their source, and specs. Every spec is marked Confirmed, Rumored, Our read or No source on file, with the source outlet and date.
    compare_productsSide-by-side specs for 2 or 3 products, from the same engine as idevice.com/compare. Each cell carries Confirmed/Rumored/Our read and its source outlet and date. Products in different categories are compared on shared structured facts only. Optional specs filters rows by keyword, e.g. ['battery','sleep'].
    get_claimsEvery well-sourced claim for one product, each with its status (Right, Partly right, Wrong, Never settled, Not comparable, Not checked yet, No outcome yet), how many outlets reported it, who reported it first, and a link to the evidence on idevice.com.
    search_claimsFind well-sourced claims by keyword across every tracked product, e.g. 'battery', 'display', 'price'. Each result carries its status and product lifecycle.