# Matter DCL MCP Server (`firedanceio/matter-dcl-mcp`) Actor

Hosted MCP server for AI assistants: look up any Matter smart home device's maker, product name, device type, support links and certification in the official CSA Distributed Compliance Ledger.

- **URL**: https://apify.com/firedanceio/matter-dcl-mcp.md
- **Developed by:** [Firedance](https://apify.com/firedanceio) (community)
- **Categories:** MCP servers, AI, Developer tools
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 tool calls

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Matter DCL MCP Server

Give your AI assistant the official registry of every Matter smart home device. This hosted **MCP server** connects
Claude, Cursor, VS Code and other MCP clients to the **CSA Distributed Compliance Ledger** (DCL), so you can ask:

- "Who makes the Matter device with Vendor ID 0x100B, Product ID 0x2184?"
- "Is this light certified, and for which Matter version?"
- "What Vendor ID does Eve use, and what products have they registered?"

No install and no extra keys: connect with your Apify token and start asking.

### Connect

Server URL (Streamable HTTP):

```
https://firedanceio--matter-dcl-mcp.apify.actor/mcp
```

Send your Apify API token as a Bearer token. For example, in Claude Code:

```bash
claude mcp add --transport http matter-dcl https://firedanceio--matter-dcl-mcp.apify.actor/mcp --header "Authorization: Bearer YOUR_APIFY_TOKEN"
```

Most MCP clients take the same URL and header in their server settings.

### Tools

| Tool | What it does |
|---|---|
| `dcl_lookup_device` | Everything about a device from its Vendor ID and Product ID: maker, product, device type, links, certification |
| `dcl_get_vendor` | The company registered under a Vendor ID |
| `dcl_search_vendors` | Find Vendor IDs by company or brand name (Hue and WiZ map to Signify, LIFX to Feit Electric) |
| `dcl_get_product` | A product's name, part number, device type, support and manual links, pairing and reset hints |
| `dcl_list_vendor_products` | Every product a vendor has registered |
| `dcl_get_certification` | Certification status, certificate ID, date, Matter version and transport |

IDs can be decimal (`4107`) or hex (`0x100B`). They come from a device's DNS-SD record (`VP=4107+8580`), its Basic
Information cluster or the onboarding payload in its QR code. All tools are read-only.

### Pricing

Pay per result: **$0.002 per successful tool call** ($2 per 1,000). Lookups that fail aren't charged, and platform usage
is included in the price.

### Run it yourself

The server is open source: [matter-dcl-mcp](https://github.com/firedanceio/matter-dcl-mcp) runs locally over stdio with
`npx -y github:firedanceio/matter-dcl-mcp`. Need bulk lookups instead of chat? Use
[Matter Device Lookup](https://apify.com/firedanceio/matter-device-lookup).

### Notes

- Data is read live from the public DCL (`on.dcl.csa-iot.org`). Nothing is stored.
- Not affiliated with the Connectivity Standards Alliance.
- Built by [Firedance](https://firedance.io), who make FirePod, a speaker that syncs smart lights to music. More of our
  open source smart home tools: [firedance.io/open-source](https://firedance.io/open-source/).

# Actor input Schema

## `network` (type: `string`):

The production ledger (mainnet) or the test ledger (testnet).

## Actor input object example

```json
{
  "network": "mainnet"
}
```

# Actor output Schema

## `mcpServer` (type: `string`):

Connect your MCP client here (Streamable HTTP), with your Apify token as a Bearer token.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("firedanceio/matter-dcl-mcp").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("firedanceio/matter-dcl-mcp").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call firedanceio/matter-dcl-mcp --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,firedanceio/matter-dcl-mcp"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/CPnRzLit5guZhzpgP/builds/NpTLVTG6vNQxKlWbn/openapi.json