INDIVIDUAL MCP TOOL

add_field

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

chatdatasync.comnone authenticationAvailability not checked

Input schema

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

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.

get_sync_context — Returns the tracker name, default table, available tables, and field definitions scoped to the supplied API key.
list_records — Preferred structured retrieval tool after get_sync_context.
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.
summarize_records — Preferred summary tool after get_sync_context when you can map the request to exact field filters.
get_record — Reads one record from the API-key scoped tracker by ID.
create_record — Creates one record in the API-key scoped tracker.
update_record — Updates one record in the API-key scoped tracker by ID using a partial field patch.
update_records — Updates many records in one call by applying a partial field patch to each.