MCP server
RemoteLock MCP by usefulapi
Read RemoteLock devices and guests; manage door access and physically lock or unlock…
- Runs
- Remotely
- Version
- 1.11.0
- Listing updated
- 4 days ago
About RemoteLock MCP by usefulapi
RemoteLock MCP by usefulapi is an MCP server. It runs as a hosted remote server, so there is nothing to install locally.
Read RemoteLock devices and guests; manage door access and physically lock or unlock doors.
Install
Run in a terminal
claude mcp add --transport http remotelock https://remotelock.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://remotelock.usefulapi.io/mcpInstall in CursorOpens Cursor, which asks you to confirm. Or add it by hand:
Add to ~/.cursor/mcp.json
{
"mcpServers": {
"remotelock": {
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:
Add to .vscode/mcp.json
{
"servers": {
"remotelock": {
"type": "http",
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"remotelock": {
"serverUrl": "https://remotelock.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"remotelock": {
"type": "http",
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Tools this server provides (20)
Read directly from the server.
- remotelock_get_account
- The RemoteLock account these credentials belong to: name, plan limits and settings. Use it to confirm which account is connected. GET /account.
- remotelock_list_locations
- List the account's locations (properties/sites) with address and time zone. Use the ids to filter devices. GET /locations.
- remotelock_get_location
- One location by id. GET /locations/{id}.
- remotelock_list_devices
- List devices: locks, access-control doors, thermostats, etc., with name, model, battery/connectivity state, lock state and location. Filter by type (e.g. lock) or location. GET /devices.
- remotelock_get_device
- One device (lock) by id with its full state: connectivity, battery/power, lock state, auto-lock settings, model and location. GET /devices/{id}.
- remotelock_lock_device
- WRITE: sends the lock command to a lock (it locks the door). Locking an already locked door changes nothing. PUT /devices/{id}/lock.
- remotelock_unlock_device
- WRITE, 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 specific door, and set confirm to true. PUT /devices/{id}/unlock.
- remotelock_list_access_persons
- List the people who can open doors: access users (permanent) and access guests (time-limited), with name, email, status, validity window and their PIN / card number. By default only current and upcoming people; pass status to include expired or deactivated. GET /access_persons.
- remotelock_get_access_person
- One access user or guest by id, with status, validity window and PIN / card number. GET /access_persons/{id}.
- remotelock_create_access_user
- WRITE: 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 give them doors. The reply includes the PIN. Check remotelock_list_access_persons first to avoid duplicates. POST /access_persons.
- remotelock_create_access_guest
- WRITE: 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_grant_access to give them doors. The reply includes the PIN. POST /access_persons.
- remotelock_deactivate_access_person
- WRITE: 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 deleted. Only do it when the user asked. PUT /access_persons/{id}/deactivate.
- remotelock_list_person_accesses
- List 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_accesses
- List 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_access
- WRITE: 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). Optionally limit the hours with an access schedule (access_schedule_id, for recurring daily hours) or override a guest's start/end time of day on this door. POST /access_persons/{id}/accesses.
- remotelock_revoke_access
- WRITE: 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 person itself stays. Only do it when the user asked. DELETE /access_persons/{id}/accesses/{access_id}.
- remotelock_list_door_groups
- List door groups (named sets of locks you can grant access to in one step). GET /groups.
- remotelock_list_group_items
- List the items (locks) that belong to one door group. GET /groups/{id}/items.
- remotelock_list_notifications
- List notifications sent by notification subscriptions: each names the lock (publisher), the event type (unlocked, access_denied, jammed, power_level_low, ...) and an event_id. Only events that match a subscription appear. Get details with remotelock_get_event. GET /notifications.
- remotelock_get_event
- One 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 not returned. GET /events/{id}.
RemoteLock MCP by usefulapi FAQ
How do I add RemoteLock MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http remotelock https://remotelock.usefulapi.io/mcp