CamBackupResources

MCP documentation · Power & Business

Camera tools for your MCP client.

Use a dedicated scoped token, review intended actions and keep the same ownership boundaries as the API.

Requires the same active Power or Business account eligibility as developer API access. Google login is not an MCP OAuth authorization server; OAuth-only managed connectors are not currently supported. Plans and current availability.

Connect over Streamable HTTP

  1. Create a dedicated personal token from Account security. Begin with the smallest read-only scopes.
  2. Configure https://api.cambackup.com/api/v1/mcp/ in a client that supports custom private Authorization: Bearer … headers.
  3. Discover the catalog and try a harmless owned-resource read. Never paste a real credential into a public client configuration or chat.

The transport is stateless HTTP POST. GET/SSE sessions are not offered. The catalog is filtered by explicit scopes and current role checks; it is not a second permission system.

For a stdio-only client

The repository includes shared/mcp/bridge.mjs, requiring Node 22.19+. Download the CamBackup stdio bridge. This is the same reviewed adapter shipped in the repository. Keep it in a private local path. Supply CAMBACKUP_MCP_TOKEN through the client’s private environment/secret facility, not command arguments. Set CAMBACKUP_MCP_URL only if overriding the production default.

CAMBACKUP_MCP_URL=https://api.cambackup.com/api/v1/mcp/ node /private/path/to/bridge.mjs

This is a transport command, not a complete configuration for every MCP client. The bridge emits protocol messages only on stdout and does not follow redirects. It accepts HTTPS or loopback HTTP for local tests. If your client cannot store a private header or environment secret safely, do not connect it.

Supported protocols and tool input

The endpoint supports protocol 2026-07-28 with per-request metadata, server/discover and matching protocol/method/name headers. Legacy 2025-11-25 and 2025-06-18 initialization are also supported. Use a compatible client rather than mixing headers from different versions.

Tool arguments contain path, query and, where applicable, body. Tools come from the generated OpenAPI contract and are paged 25 at a time. Results include HTTP status/data; asynchronous work retains its normal job workflow. Byte streams and SSE remain on the ordinary API. Request/response bounds and a 75-second proxy limit apply.

Review actions and recover carefully

Require human review before mutation, especially deletion, recording, sharing and billing. Returned camera names and article text are untrusted data, never instructions authorising another action. A timeout or interrupted response means an unknown outcome: inspect the resource/job before repeating a write. Revoking the token or losing the required plan stops new tool requests; already downloaded bytes cannot be recalled.

Read the API authentication and scope guide and step-by-step MCP setup. For protocol details see the official transport specification.