MCP server

Dib speaks the Model Context Protocol. Drop your API key into Claude Desktop, Cursor, or any MCP-aware client and your home becomes a tool the model can call.

Connect in one click

Pick your client below. Cursor and VS Code install Dib instantly; for Claude Code, Claude Desktop, and ChatGPT, copy the command or URL and drop it into their connector settings. Either way you'll sign in and pick your home the first time you connect.

Endpoint

https://dib.io/api/mcp

Connect with OAuth (recommended)

The easiest way in: just add the server URL to your client. When the client connects, Dib walks you through signing in, picking which home to connect, and choosing what it can access. No keys to copy or paste.

Under the hood we speak OAuth 2.1 the way MCP clients expect: protected resource metadata at /.well-known/oauth-protected-resource, authorization server metadata at /.well-known/oauth-authorization-server, dynamic client registration, and PKCE. Most clients (Claude, Cursor, VS Code, ChatGPT) handle all of that for you the moment you paste the URL.

{
  "mcpServers": {
    "dib": {
      "url": "https://dib.io/api/mcp"
    }
  }
}

When you approve, the token Dib issues is scoped to the home and the permissions you picked, and you can revoke it any time from your API key settings. Connecting a client needs a Pro home with the Public API enabled.

Or bring your own API key

Prefer to manage credentials yourself? Authenticate with the same Authorization: Bearer header you use for REST.

Claude Desktop

Add the following to your ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "dib": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://dib.io/api/mcp"],
      "env": {
        "AUTHORIZATION": "Bearer dib_live_..."
      }
    }
  }
}

Cursor

Add an entry to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "dib": {
      "url": "https://dib.io/api/mcp",
      "headers": { "Authorization": "Bearer dib_live_..." }
    }
  }
}

Tools exposed

The MCP server mirrors the REST API and is gated by the same scopes: a tool only works if your key carries the matching scope (reads need :read, writes need :write).

• dib_search — natural-language search across all resources.
• Inventory: dib_list_inventory, dib_get_inventory_item, dib_create_inventory
• Vehicles: dib_list_vehicles, dib_get_vehicle, dib_create_vehicle
• Tasks: dib_list_tasks, dib_create_task, dib_update_task
• Documents: dib_list_documents, dib_get_document, dib_create_document
• Rooms: dib_list_rooms
• Home profile: dib_get_property, dib_update_property

Read-only key? The write tools simply won't fire. Mint a key with the relevant :write scopes and the server picks them up automatically — no config change needed.

Things to try

The MCP server gets really fun once Dib is one tool among many. When your assistant can also reach your email, calendar, files, or a shopping site, it can stitch them together and do the boring parts for you. A few prompts to spark ideas:

Turn email receipts into inventory

“Search my Gmail for purchase receipts from the last two years, pull out the appliances and electronics, and add each one to my Dib inventory with the brand, model, price, and purchase date.”

Pair Dib with a Gmail or email MCP and your assistant reads the receipts, then calls dib_create_inventory for each item it finds. No more typing in serial numbers by hand.

File the warranty PDF before you lose it

“Grab the warranty PDF in my Downloads folder, figure out which appliance it belongs to, and save it to that item in Dib.”

With a filesystem MCP alongside Dib, the model reads the document, matches it to the right inventory item, and stores it with dib_create_documentso it's there when you need to make a claim.

Put maintenance on your calendar

“Look at my open Dib tasks, then add calendar reminders for the HVAC filter and the gutter cleaning so I actually do them.”

Combine dib_list_taskswith a calendar MCP and Dib's reminders show up right next to the rest of your week.

Reorder the consumables you're running low on

“Check my Dib inventory for air filters and water filters, look up the matching sizes, and start a cart with replacements.”

Dib remembers the exact model numbers, so a shopping or browser MCP can find the right part instead of guessing.

Build a moving or insurance packet

“List everything in my living room from Dib, total up the estimated value, and drop it into a spreadsheet I can send to my insurer.”

Read with dib_list_inventory, then hand the results to a Google Sheets or Notion MCP for a tidy, shareable document.

Catch up after a busy week

“Forward the home-related emails from this week to Dib: log the plumber's invoice as a document, add a task to follow up on the quote, and note the new dishwasher in my kitchen inventory.”

One prompt, three tools, a home that stays up to date without you babysitting it.

The pattern is always the same: let your assistant gather context from wherever it lives, then use Dib's tools to remember it. Mix and match whatever MCP servers you already have connected.