Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Read RemoteLock devices and guests; manage door access and physically lock or unlock doors.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Funciona en Claude para web, escritorio y móvil:
https://remotelock.usefulapi.io/mcpEjecuta esto en tu terminal
claude mcp add --transport http remotelock https://remotelock.usefulapi.io/mcpPégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"remotelock": {
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"remotelock": {
"type": "http",
"url": "https://remotelock.usefulapi.io/mcp"
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
ChatGPT solo se conecta a servidores en internet:
https://remotelock.usefulapi.io/mcpLos nombres de los menús pueden variar un poco según el plan y con el tiempo.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.
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) or location. GET /devices.
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 specific door, and set confirm to true. PUT /devices/{id}/unlock.
remotelock_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 number. By default only current and upcoming people; pass status to include expired or deactivated. GET /access_persons.
remotelock_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 give them doors. The reply includes the PIN. Check remotelock_list_access_persons first to avoid duplicates. POST /access_per
remotelock_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_grant_access to give them doors. The reply includes the PIN. POST /access_persons.
remotelock_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 deleted. Only do it when the user asked. PUT /access_persons/{id}/deactivate.
remotelock_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). Optionally limit the hours with an access schedule (access_schedule_id, for recurring daily hours) or override a guest's s
remotelock_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 person itself stays. Only do it when the user asked. DELETE /access_persons/{id}/accesses/{access_id}.
remotelock_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, ...) and an event_id. Only events that match a subscription appear. Get details with remotelock_get_event. GET /notifications.
remotelock_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 not returned. GET /events/{id}.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio usefulapi.io (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Respondió en 387 ms (HTTP 200)
No hace falta iniciar sesión
Leímos 20 descripciones de herramientas y no encontramos instrucciones ocultas para la IA
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en la nube del creador. Te conectas por internet sin instalar nada, pero lo que envías pasa por los servidores del creador.
El repo de GitHub cambió por última vez –, y la última versión (1.6.3) llegó al registro ayer.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también funcionan las apps que aceptan servidores MCP remotos, como ChatGPT en modo desarrollador.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Connect a dedicated app for your API-enabled RemoteLock account.
https://remotelock.usefulapi.io/mcp.claude mcp add --transport http remotelock https://remotelock.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "remotelock": { "url": "https://remotelock.usefulapi.io/mcp" } } }
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, and the login page asks for your RemoteLock credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/remotelock/
| Tool | Type | What it does |
|---|---|---|
remotelock_get_account | read | Get account |
remotelock_list_locations | read | List locations |
remotelock_get_location | read | Get location |
remotelock_list_devices | read | List devices (locks) |
remotelock_get_device | read | Get device |
remotelock_lock_device | write | Lock a lock |
remotelock_unlock_device | write | Unlock a lock |
remotelock_list_access_persons | read | List access users and guests |
remotelock_get_access_person | read | Get access user or guest |
remotelock_create_access_user | write | Create a permanent access user |
remotelock_create_access_guest | write | Create a time-limited access guest |
remotelock_deactivate_access_person | write | Deactivate an access user or guest |
remotelock_list_person_accesses | read | List a person's door access |
remotelock_list_device_accesses | read | List who can open a lock |
remotelock_grant_access | write | Grant door access |
remotelock_revoke_access | write | Revoke door access |
remotelock_list_door_groups | read | List door groups |
remotelock_list_group_items | read | List the locks in a door group |
remotelock_list_notifications | read | List notifications (activity) |
remotelock_get_event | read | Get event |
remotelock_usage_status | meta | Usage status (free-tier meter) |
remotelock_request_feature | meta | Request a missing feature |
remotelock_upgrade | meta | Upgrade to Pro or Pro+ |
remotelock_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per RemoteLock account) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this 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 support@usefulapi.io.
MIT