RMCP.DEV
← Registry

Developer Tools

chatdatasync.com

Provides structured access to a tracker's records and tables via API key.

1 endpoint14 known toolsFirst detected June 3, 2026Last detected July 9, 2026

ENDPOINT 1

https://chatdatasync.com/api/mcp

No auth detected

Known tools 14

get_sync_context

Returns the tracker name, default table, available tables, and field definitions scoped to the supplied API key.

Inferred read-only
list_records

Preferred structured retrieval tool after get_sync_context.

Inferred read-only
search_records

Fallback retrieval tool for broad natural-language requests when you cannot confidently map the request to exact table fields from get_sync_context.

Inferred read-only
summarize_records

Preferred summary tool after get_sync_context when you can map the request to exact field filters.

Inferred read-only
get_record

Reads one record from the API-key scoped tracker by ID.

Inferred read-only
create_record

Creates one record in the API-key scoped tracker.

Inferred read-only
update_record

Updates one record in the API-key scoped tracker by ID using a partial field patch.

Inferred read-only
update_records

Updates many records in one call by applying a partial field patch to each.

Inferred read-only
delete_record

Deletes one record from the API-key scoped tracker by ID.

Inferred read-only
list_trackers

Lists every tracker connected to this account, with each tracker's name, description, and ID.

Inferred read-only
create_tracker

Creates a new tracker on this account so the user can keep more than one kind of list from the same connection.

Inferred read-only
describe_schema

Returns the full editable layout of a tracker: every section (table), its fields with their type (text | number | boolean | date | time | choice | reference), whether each field is required, the allowed values for choice fields, and which section a reference field links to.

Inferred read-only
add_section

Adds a new section (table) to a tracker's layout, up to the account's plan limit.

Inferred read-only
add_field

Adds a new field to a section in a tracker's layout, up to the per-section field limit.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.chatdatasync-com]
url = "https://chatdatasync.com/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "chatdatasync-com": {
      "type": "http",
      "url": "https://chatdatasync.com/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: chatdatasync-com
Remote MCP URL: https://chatdatasync.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "chatdatasync-com": {
      "url": "https://chatdatasync.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "chatdatasync-com": {
      "type": "http",
      "url": "https://chatdatasync.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "chatdatasync-com",
  "transport": "streamable-http",
  "url": "https://chatdatasync.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for chatdatasync.com was fetched 2026-09-12T00:36:24.223Z.

Trust status Trusted

chatdatasync.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.