Device Specs MCP Server
# Device Specs MCP Server
[](https://www.npmjs.com/package/@granturismo/devicespecs-mcp)
[](https://www.nuget.org/packages/DeviceSpecs.Mcp)
[](https://opensource.org/licenses/MIT)
A [Model Context Protocol](https://modelcontextprotocol.io) server that gives Claude, Cursor, VS Code Copilot and any other MCP client grounded access to the **[Device Specs API](https://ds.gtgroup.dev)**: 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/`](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.
## 2. Add the server to your client
### Claude Desktop
Edit `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`, Windows: `%APPDATA%\Claude\`):
```json
{
"mcpServers": {
"devicespecs": {
"command": "npx",
"args": ["-y", "@granturismo/devicespecs-mcp"],
"env": {
"DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY"
}
}
}
}
```
### Claude Code
```bash
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):
```json
{
"mcpServers": {
"devicespecs": {
"command": "npx",
"args": ["-y", "@granturismo/devicespecs-mcp"],
"env": { "DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY" }
}
}
}
```
### VS Code (Copilot agent mode)
`.vscode/mcp.json`:
```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)
```json
{
"mcpServers": {
"devicespecs": {
"command": "dnx",
"args": ["DeviceSpecs.Mcp", "--yes"],
"env": { "DEVICESPECS_API_KEY": "YOUR_RAPIDAPI_KEY" }
}
}
}
```
```bash
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
```bash
# 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).
## Links
- Website and docs: https://ds.gtgroup.dev and https://ds.gtgroup.dev/docs
- Other SDKs: [TypeScript](https://github.com/GranTurismo/DeviceSpecs-npm) (`npm i @granturismo/devicespecs`), [Python](https://github.com/GranTurismo/DeviceSpecs-python) (`pip install devicespecs`), [.NET](https://github.com/GranTurismo/DeviceSpecs-nuget) (`dotnet add package DeviceSpecs`)
- Get an API key: https://rapidapi.com/controller2042000/api/gsmarenaparser
## License
MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.