Give Claude an organized place to save and find your entries. ChatData Sync connects your tracker through a connector, so you can log an update or ask a question in chat.
A connector lets Claude use an outside tool, such as your tracker. MCP is the connection standard behind it; you do not need to learn the protocol to follow setup.
Use ChatData Sync sign-in when your client offers it. Review which trackers it requests access to. Manual clients may instead ask for a URL and a custom header named x-api-key. Keep that key private; do not paste it as an OAuth bearer token.
Sign in to ChatData Sync and describe what you want to track in plain English. Your structured tracking space is suggested from your description. Review it before creating the tracker.
Navigate to the Connect tab in your new tracking space. You will see an MCP endpoint URL and a scoped security token. For direct MCP clients, that token belongs in the custom x-api-key header.
Look for Connectors in Claude settings and add the URL shown on your Connect tab. If sign-in is offered, use it and review the access request. For a client with manual header settings, use x-api-key with your tracker key. Menu names and connector availability depend on your Claude client and plan.
Ask Claude to log a new entry, retrieve records from last month, update a status, or summarize patterns. Ask Claude to read back the saved entry and check the details.
A tracker-specific connection accesses one tracker. Some hosted sign-in connections request broader access to your own trackers; review what you authorize. You can revoke a named connection or remove a hosted authorization from your dashboard.
When Claude retrieves tracker information, its provider processes that information under its own terms and privacy policy. Only connect tools you trust.
Start free — describe your tracker and follow the guided connection steps for Claude. No credit card required.
Start free today