Skip to main content
Glama
Device Specs MCP Server

Device Specs MCP Server

by GranTurismo

Device Specs MCP Server

NPM Version NuGet Version License: MIT

A Model Context Protocol server that gives Claude, Cursor, VS Code Copilot and any other MCP client grounded access to the Device Specs API: normalized hardware specifications for 10,000+ smartphones from Apple, Samsung, Google, Xiaomi, OnePlus, vivo, Oppo, Motorola, Sony, Nothing and 25+ more brands.

Ask things like:

  • "What's the battery and charging speed on the Galaxy S24 Ultra?"

  • "Find phones with a headphone jack, 5000 mAh and 120 Hz under 200 g."

  • "Which phone is model number SM-S928B?"

  • "Compare the Pixel 9 Pro and the iPhone 15 Pro."

Runs over stdio. Two interchangeable builds with the same seven tools:

Build

Run

Needs

npm @granturismo/devicespecs-mcp

npx -y @granturismo/devicespecs-mcp

Node 18+

NuGet DeviceSpecs.Mcp (source in dotnet/)

dnx DeviceSpecs.Mcp --yes

.NET 10 SDK

Every example below uses the npm build; for the .NET build replace the command with dnx and the args with ["DeviceSpecs.Mcp", "--yes"].

1. Get an API key

The server talks to the API through RapidAPI. Create a free key (no card required) at https://rapidapi.com/controller2042000/api/gsmarenaparser and keep it handy.

Related MCP server: DocAgent-MCP

2. Add the server to your client

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

{
  "mcpServers": {
    "devicespecs": {
      "command": "npx",
      "args": ["-y", "@granturismo/devicespecs-mcp"],
      "env": {
        "DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY"
      }
    }
  }
}

Claude Code

claude mcp add devicespecs -e DEVICESPECS_API_KEY=YOUR_RAPIDAPI_KEY -- npx -y @granturismo/devicespecs-mcp

Cursor

.cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "devicespecs": {
      "command": "npx",
      "args": ["-y", "@granturismo/devicespecs-mcp"],
      "env": { "DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY" }
    }
  }
}

VS Code (Copilot agent mode)

.vscode/mcp.json:

{
  "servers": {
    "devicespecs": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@granturismo/devicespecs-mcp"],
      "env": { "DEVICESPECS_API_KEY": "${input:devicespecs-key}" }
    }
  },
  "inputs": [
    { "id": "devicespecs-key", "type": "promptString", "description": "Device Specs API key", "password": true }
  ]
}

.NET build (NuGet)

{
  "mcpServers": {
    "devicespecs": {
      "command": "dnx",
      "args": ["DeviceSpecs.Mcp", "--yes"],
      "env": { "DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY" }
    }
  }
}
claude mcp add devicespecs -e DEVICESPECS_API_KEY=YOUR_RAPIDAPI_KEY -- dnx DeviceSpecs.Mcp --yes
# or install once as a global tool, then use "command": "devicespecs-mcp"
dotnet tool install -g DeviceSpecs.Mcp

dnx ships with the .NET 10 SDK and downloads the package on first use. On NuGet.org the package is listed under the "MCP Server" filter, and VS Code / Visual Studio can add it from the package page.

Tools

Tool

What it does

get_phone_specs

Full (or compact) specification sheet for one phone by manufacturer + model.

search_phones

Filter the whole catalog by hardware criteria (RAM, battery, refresh rate, NFC, headphone jack, price, chipset, ...).

list_phones_by_manufacturer

Every model from one brand, paged, with key specs.

list_phones_by_chipset

Every phone using a given SoC.

lookup_model_number

Resolve a hardware code such as SM-S928B to its marketing name and specs.

compare_phones

Side-by-side key specs for 2 to 4 phones plus a differences map.

list_filter_properties

Offline reference of the filter language (operators, properties, aliases, examples).

A resource devicespecs://filters exposes the same filter reference as Markdown.

Filter language in one line

search_phones takes filters as a JSON object of "<property>[_<operator>]": value, for example {"manufacturer":"Samsung","ram_gte":12,"refresh_rate_gte":120,"battery_gte":5000,"headphone_jack":true}. Operators: _gt, _gte, _lt, _lte, _contains, _in (comma list), _between ("min,max"), _has. Full property list: call list_filter_properties or read https://ds.gtgroup.dev/docs.

Configuration

Variable

Default

Purpose

DEVICESPECS_API_KEY

(none)

Your RapidAPI key. Required when using the default gateway.

DEVICESPECS_BASE_URL

https://gsmarenaparser.p.rapidapi.com/

API gateway base URL. Point it at another host if you self-host or have a direct contract.

DEVICESPECS_API_HOST

gsmarenaparser.p.rapidapi.com

Value sent in x-rapidapi-host.

Without a key the data tools return a clear error with the sign-up link; list_filter_properties always works offline.

Development

# npm build
npm install
npm run build
DEVICESPECS_BASE_URL=https://dsapi.gtgroup.dev/ npm run smoke   # end-to-end stdio test

# .NET build (same smoke test, pointed at the compiled server)
dotnet build dotnet/DeviceSpecs.Mcp -c Release
DEVICESPECS_BASE_URL=https://dsapi.gtgroup.dev/ MCP_COMMAND=dotnet MCP_ARGS='["dotnet/DeviceSpecs.Mcp/bin/Release/net10.0/devicespecs-mcp.dll"]' npm run smoke
dotnet pack dotnet/DeviceSpecs.Mcp -c Release -o out   # DeviceSpecs.Mcp.<version>.nupkg

Releases: push a v* tag to publish the npm package and a nuget-v* tag to publish the NuGet package (see .github/workflows). server.json describes both packages for the official MCP registry (https://github.com/modelcontextprotocol/registry).

License

MIT

Available Tools

7 tools
compare_phonesCompare phones side by sideA
Read-onlyIdempotent

Fetch two to four phones and return their key specs side by side plus a 'differences' map containing only the fields whose values differ, which is the quickest way to answer 'X vs Y' questions. Each phone is given as manufacturer + model in catalog spelling.

Inputs: phones (required).

get_phone_specsGet phone specificationsA
Read-onlyIdempotent

Return the specification sheet for one smartphone by manufacturer and model name. Includes display (size, panel, refresh rate, brightness), chipset/CPU/GPU, RAM and storage options, battery capacity and charging, cameras, dimensions and weight, IP rating, connectivity (NFC, Bluetooth, USB, Wi-Fi), sound, benchmark scores, EU energy label, launch prices, colours and hardware model numbers. Model names follow catalog spelling, e.g. manufacturer='Samsung' model='Galaxy S24 Ultra', manufacturer='Apple' model='iPhone 15 Pro', manufacturer='Google' model='Pixel 9 Pro'.

Inputs: model (required), manufacturer (required), compact.

list_filter_propertiesFilter language referenceA
Read-onlyIdempotent

Return the complete reference for the search_phones filter language: all operators (_gt, _gte, _lt, _lte, _contains, _in, _between, _has), every filterable property with its aliases, type and JSON path, usage notes and worked examples. No network call. Use it before composing a non-trivial search.

Inputs: no named parameters.

list_phones_by_chipsetList phones by chipsetA
Read-onlyIdempotent

List phones powered by a given system-on-chip. The chipset must match the catalog string exactly (case-insensitive), e.g. 'Google Tensor G4', 'Apple A17 Pro', 'Qualcomm SM8650-AC Snapdragon 8 Gen 3', 'Mediatek Dimensity 9300'. If you only know part of the name, use search_phones with {"chipset_contains":"Snapdragon 8 Gen 3"} instead.

Inputs: chipset (required), limit, offset, compact.

list_phones_by_manufacturerList phones by manufacturerA
Read-onlyIdempotent

List every phone in the catalog from one brand, with key specs for each. Useful to discover exact model names before calling get_phone_specs, or to browse a brand's line-up. Large brands have hundreds of models (Samsung ~1,500), so use limit/offset to page.

Inputs: manufacturer (required), limit, offset, compact.

lookup_model_numberIdentify a phone from its model numberA
Read-onlyIdempotent

Resolve a hardware model/variant code (the string printed on the device or returned by Android's Build.MODEL, e.g. 'SM-S928B', 'A3106', 'GP8GD', '2201116SG', 'TA-1004') to its marketing name, manufacturer and chipset, and return the full specification sheet when found.

Inputs: model_number (required), compact.

search_phonesSearch phones by hardware filtersA
Read-onlyIdempotent

Find smartphones matching hardware criteria using the API's filter language: keys are '[_]' and values are strings, numbers or booleans. Operators: (none)=equals, _gt, _gte, _lt, _lte, _contains, _in (comma list), _between ('min,max'), _has. Common properties: manufacturer, model, chipset, ram (GB), storage (GB), battery (mAh), refresh_rate (Hz), displaysize (inches), panel_type, brightness (nits), charging (W), wireless_charging, weight (g), ip_rating, nfc, headphone_jack, card_slot, stereo_speakers, infrared, price_usd, announcedate, android. Example: {"manufacturer":"Samsung","ram_gte":12,"refresh_rate_gte":120,"battery_gte":5000}. All filters are ANDed. Call list_filter_properties for the complete list of properties and aliases. Results come back in catalog order (roughly newest first within a brand).

Inputs: filters (required), limit, offset, compact.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct retrieval strategy: exact spec lookup, filtered search, brand listing, chipset listing, model-code resolution, and side-by-side comparison. The only real overlap is that search_phones can approximate list_phones_by_manufacturer and list_phones_by_chipset, but the descriptions explicitly route users between them (e.g. pointing to search_phones with chipset_contains when the exact chipset string is unknown). list_filter_properties is a helper for search_phones rather than a competing operation, so confusion risk is low.

    Naming Consistency5/5

    All seven names follow a snake_case verb_noun pattern (get_, search_, list_, lookup_, compare_), with list_phones_by_manufacturer and list_phones_by_chipset forming a clean parallel pair. No camelCase or case-mixing anywhere.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each earns its place: lookup by name, filtered search, two browse axes, code resolution, comparison, and filter reference. Nothing looks like a redundant wrapper.

    Completeness4/5

    The surface covers the full read-only lifecycle for a hardware catalog: discovery (search/list), precise retrieval (get_specs), identifier resolution (lookup_model_number), and multi-item comparison, plus documentation of the filter language. Minor gaps remain with no direct enumeration of brands, chipsets, or a paginated full-catalog dump, and compare is capped at four phones, but agents can work around these via search_phones.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    • MCP server of "Usilitel Signala" (usilitel-signala.ru), an online shop and installer of cellular signal boosters in Moscow and the Moscow region, Russia. It gives AI assistants live, read-only access to the catalog: repeaters, ready-made kits, boosters, antennas, coaxial cable and cable assemblies, 4G routers and accessories from VEGATEL, Baltic Signal, DalSvyaz and KROKS — more than 1,100 products. Features: • product search and comparison with live prices and stock (synced with the website every 5 minutes); • equipment picks for a site: area, mobile operator or frequency band, calls or internet; • texts of catalog sections, collections, installation services and blog articles; • recent catalog changes: new products, price and stock updates; • contacts, delivery, payment and returns; • a link to the order form on the website, pre-filled with the selection — the customer enters the phone number on the website; no personal data passes through the assistant. Read-only, no authentication required. Data language: Russian.

    • AgentReady Tools is a searchable catalog of more than 250 APIs, MCP servers and developer tools that AI agents can use, each with agent-readiness checks (docs, auth, OpenAPI, MCP support). Search by task, get tool details and related tools, and read or share field notes from other agents in the Agent Community. Remote MCP endpoint: https://agentready-tools.com/mcp

      https://agentready-tools.com/mcp
    • Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.

      https://api.algenta.ai/mcp
    • IPStack MCP Adapter turns IPStack's REST APIs into Model Context Protocol tools so any MCP-compatible client can call them directly in conversation. The first release ships IPStack IP geolocation and security lookups (single IP, caller's IP, and bulk). Additional APILayer services are added by registering them in a single config file, so the catalog grows without client-side changes.

      https://mcp.apilayer.com/mcp

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language queries on technical specifications and automated code compliance checks using local RAG with vector search, integrated via MCP.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables local document question-answering and retrieval via MCP, supporting multi-turn conversation, intent recognition, and tools for document search, Q&A, and summarization.
      5
      -
    • F
      license
      C
      quality
      C
      maintenance
      Exposes Spec-Driven Development specs and reusable skills to MCP clients, enabling them to validate specs, list and fetch skills, and generate ready-to-use prompts for code generation.
      16
      -