---
title: "Developer overview"
description: "Connect to Cadence with MCP: tracking data, scoped edits, authentication, and integration boundaries."
canonical_url: https://cadence-me.com/developers
last_updated: 2026-10-18
status: stable
source: src/data/developers.ts
---

# Developer overview

Cadence's MCP server lets an authorized client read a person's tracking record and make specific edits at their direction.

## Availability

Local implementation verified. Hosted launch, live Claude and ChatGPT acceptance, and directory approval are pending. These pages describe contract 1.7.0 and the implementation verified on October 18, 2026. They do not announce a public launch.

The planned endpoint is **https://app.cadence-me.com/mcp**. The OAuth issuer is **https://app.cadence-me.com**. Use an operator-provided test deployment until hosted acceptance is complete. A local installation needs its own configured issuer and enabled integration endpoints.

## What you can build

Read Behaviors, categories, schedules, Occurrences, notes, status history, time sessions and adherence. With separate permissions, mark an Occurrence, edit its note, or create, edit, archive and restore a Behavior. There are no delete tools, category writes, account changes or reminder-delivery controls.

Start with [quickstarts](/developers/quickstarts), then use the [tool reference](/developers/tools). Read [authentication](/developers/authentication) before building a client, and [safe retries](/developers/idempotency) before writing data.

## Transport

One remote HTTP endpoint exposes 16 tools. The official MCP SDK serves protocol 2026-07-28 and stateless legacy versions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 and 2024-10-07. Use an SDK for protocol headers and negotiation.

Modern clients use server/discover; legacy clients initialize before tools/list. Successful calls contain structuredContent and a short text result. Legacy transport may use SSE responses. Cadence has no sessions, resumption, unsolicited messages, resources, prompts or MCP Apps widgets. Authenticated GET and DELETE requests return 405.

## Boundaries

Each connection belongs to one account. Account-free desktop data stays on the device and cannot be read through this server. Linked desktop data becomes available after synchronization. MCP changes arrive on linked desktop through the existing sync process.

Cadence runs no autonomous agent through MCP. The outside client chooses tool calls and handles user confirmation. Returned text is data, never instructions. See [data and privacy](/developers/data-and-privacy).

## Support

Report reproducible technical problems in [Cadence GitHub issues](https://github.com/emixd12/cadence/issues). Include the tool name, stable error code and client version. Omit tokens, account identifiers, notes and other personal data.

For private reports, email [privacy@identityscaffolding.com](mailto:privacy@identityscaffolding.com). The canonical [Privacy notice](https://app.cadence-me.com/privacy) and [Terms](https://app.cadence-me.com/terms) remain on the app site. MCP disclosure wording is approved for local implementation; publication and hosted launch remain pending.
