io.usefulapi/remotelock
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
RemoteLock MCP by usefulapi
Publisher-provided description
Read RemoteLock devices and guests; manage door access and physically lock or unlock doors.
Summary by lookupd
Lists and inspects smart locks, guests and access grants, and can lock, unlock or revoke door access for people.
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http remotelock https://remotelock.usefulapi.io/mcp
Codex, remote (streamable-http)
codex mcp add remotelock --url https://remotelock.usefulapi.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"remotelock": {
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (20 tools)
Publisher-provided text
remotelock_get_accountThe RemoteLock account these credentials belong to: name, plan limits and settings. Use it to confirm which account is connected. GET /account.remotelock_list_locationsList the account's locations (properties/sites) with address and time zone. Use the ids to filter devices. GET /locations.remotelock_get_locationOne location by id. GET /locations/{id}.remotelock_list_devicesList devices: locks, access-control doors, thermostats, etc., with name, model, battery/connectivity state, lock state and location. Filter by type (e.g. lock)remotelock_get_deviceOne device (lock) by id with its full state: connectivity, battery/power, lock state, auto-lock settings, model and location. GET /devices/{id}.remotelock_lock_deviceWRITE: sends the lock command to a lock (it locks the door). Locking an already locked door changes nothing. PUT /devices/{id}/lock.remotelock_unlock_deviceWRITE, SECURITY-SENSITIVE: sends the unlock command to a lock, which physically unlocks the door. Only call it when the user explicitly asked to unlock this speremotelock_list_access_personsList the people who can open doors: access users (permanent) and access guests (time-limited), with name, email, status, validity window and their PIN / card nuremotelock_get_access_personOne access user or guest by id, with status, validity window and PIN / card number. GET /access_persons/{id}.remotelock_create_access_userWRITE: creates a permanent access user (an employee, resident or owner) with a PIN and/or card. It creates the person only; use remotelock_grant_access to giveremotelock_create_access_guestWRITE: creates an access guest whose PIN/card only works between starts_at and ends_at (local time of the lock). It creates the person only; use remotelock_granremotelock_deactivate_access_personWRITE: deactivates an access user or guest, so their PIN/card stops working on every door. The person stays in the account (status deactivated) and is not deletremotelock_list_person_accessesList the doors, door groups and locations one access user or guest can open, with sync state per device. GET /access_persons/{id}/accesses.remotelock_list_device_accessesList the access users and guests who have access to one lock (and whether the PIN is synced to it). GET /devices/{id}/access_person_accesses.remotelock_grant_accessWRITE: gives an access user or guest access to a lock, a door group or a location, so their PIN/card opens it. RemoteLock then syncs the code to the lock(s). Opremotelock_revoke_accessWRITE: removes one access grant (an id from remotelock_list_person_accesses), so the person's PIN/card no longer opens that door, door group or location. The peremotelock_list_door_groupsList door groups (named sets of locks you can grant access to in one step). GET /groups.remotelock_list_group_itemsList the items (locks) that belong to one door group. GET /groups/{id}/items.remotelock_list_notificationsList notifications sent by notification subscriptions: each names the lock (publisher), the event type (unlocked, access_denied, jammed, power_level_low, ...) aremotelock_get_eventOne event by id (for example from a notification): type, time, source, status, the lock and the person involved, and the method used. The PIN or card used is no
Details
- Version: 1.8.3
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 381 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/remotelock/
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.usefulapi/remotelock)
- 62092 servers
- Last crawl: 2026-11-11T17:17:22.074Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp