Read RemoteLock devices and guests; manage door access and physically lock or unlock doors. For property operators with RemoteLock API access and a dedicated app for their own account. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"remotelock": {
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"remotelock": {
"type": "http",
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List devices at a property and inspect a lock’s connectivity, battery level and current state.
remotelock_list_locations remotelock_list_devices remotelock_get_device
List a lock’s access users and guests, then inspect a selected person’s access grants and validity window.
remotelock_list_device_accesses remotelock_get_access_person remotelock_list_person_accesses
Check for an existing guest, create a guest credential for the requested dates, then grant access to the chosen door. This changes who can enter the property.
Changes data · remotelock_list_access_persons remotelock_create_access_guest remotelock_grant_access
Inspect the intended person and deactivate their credential when requested. Their PIN or card stops working on every door.
Changes data · remotelock_get_access_person remotelock_deactivate_access_person
Inspect the intended lock, then unlock it only after an explicit request and confirmation for that door. The command physically unlocks the door.
Changes data · remotelock_get_device remotelock_unlock_device
The login page asks for your Client ID and Client Secret.
RemoteLock enables its API per account: email [email protected] and ask for API access. Then open the RemoteLock developer portal, click New OAuth Application and copy the Client ID and Client Secret (the secret is shown only once). They give this server access to your own account's locks and guest codes, so keep them private; they are used to call the RemoteLock API on your behalf. Requested guest names, door-access schedules, PINs/card numbers and device information pass to your chosen AI client and its LLM provider. When requested, tools can physically lock/unlock doors, create or deactivate guest credentials and grant or revoke door access. Connect only an account and records you are authorized to manage and share. Delete this dedicated OAuth application in RemoteLock to stop future token minting; revoke issued tokens to end existing access. Billing follows the verified RemoteLock account.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the RemoteLock connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
remotelock_get_account | read | 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 | read | 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 | read | Get location One location by id. GET /locations/{id}. |
remotelock_list_devices | read | List devices (locks) 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 | read | 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 | Lock a lock 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 | Unlock a lock 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 | read | List access users and guests 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 | read | Get access user or guest One access user or guest by id, with status, validity window and PIN / card number. GET /access_persons/{id}. |
remotelock_create_access_user | write | Create a permanent 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 | Create a time-limited 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 | Deactivate an access user or guest 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 | read | List a person's door access 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 | read | List who can open a lock 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 | Grant door 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 | Revoke door 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 | read | List door groups List door groups (named sets of locks you can grant access to in one step). GET /groups. |
remotelock_list_group_items | read | List the locks in a door group List the items (locks) that belong to one door group. GET /groups/{id}/items. |
remotelock_list_notifications | read | List notifications (activity) 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 | read | 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_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
remotelock_request_feature | Request a missing feature Tell usefulapi that the user needs something the RemoteLock tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
remotelock_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on RemoteLock (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
remotelock_cancel_subscription | Cancel the Pro subscription Cancel the caller's RemoteLock Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run remotelock_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper RemoteLock account | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this RemoteLock server only. Subscribe with remotelock_upgrade (it returns a Stripe Checkout link). Cancel any time with remotelock_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running remotelock_upgrade before then undoes the cancel. Or write to [email protected].
Check lock status and battery. Review who can open a door. Create time-limited guest access. Deactivate a former guest or contractor. Unlock a specifically requested door. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by RemoteLock. The server calls the RemoteLock API with your own RemoteLock access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your Client ID and Client Secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Client ID and Client Secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the RemoteLock API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in RemoteLock.
Yes, if you approve it. 7 of the 20 RemoteLock tools can create or change data. The other 13 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this RemoteLock server only. Cancel any time: Pro then runs to the end of the paid period. Run remotelock_usage_status to see how many calls you used.
Ask the AI to run remotelock_upgrade: it returns a Stripe Checkout link. To cancel, run remotelock_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with remotelock_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.