Meetily
Agent APIAdvanced

Pairing and LAN access

Let another device on your network reach the gateway over HTTPS, with certificate pinning and in-app approval.

By default the gateway listens only on your own machine, at 127.0.0.1:8420. Turn on LAN access to let another device on your network connect. LAN access is served over HTTPS on port 8421 and is off by default. A client running on the same machine reads the loopback token from its local file directly; it does not fetch a token over HTTP.

Pairing a device

  • The remote client calls POST /v1/pair/request (no token needed) to ask to connect.
  • You approve the request inside the Meetily app.
  • The client then polls GET /v1/pair/:id, which returns the access token once, at approval. Store it: it is shown only once.
  • A paired token expires 90 days after it is minted.

Trusting the connection (certificate pinning)

LAN uses a self-signed certificate. The client trusts it by pinning its SHA-256 fingerprint, not by a certificate authority. The CLI pair command supports --fingerprint to pin the expected fingerprint.

Managing pairings (Admin scope)

  • GET /v1/pairings lists pairing requests.
  • DELETE /v1/pairings/:id revokes a pairing. Revocation is atomic: it removes the token and deletes that client's webhooks in one step.

Revoking is silent to the client

A revoked client is not notified. Its next call simply fails with 401. Disconnecting or uninstalling an MCP client revokes that client's token, but it does not delete any webhooks the client created. See limitations and roadmap.

Last updated on

On this page