`peaka_post__data_projects_projectId_table_tableName_import` – 1 MCP server offers this tool

What it usually takes

No server marks it as only reading: treat it as able to change data.

From each publisher's own tool list. We never call a tool.

Server	Inputs	Read-only?
Peaka `co.huggingface.ramamatar/peaka` Imports data from a CSV file into a specified internal table in a given project. This endpoint accepts a `multipart/form-data` request with two parts: - file: The CSV file to be imported. - request: A JSON string describing how the CSV columns map to the table's columns. CSV file format can be get from `/projects/{projectId}/table/{tableName}/sample`. #### Request JSON syntax The `request` part must contain: - `mappings`: A list of objects, each with: - `name`: The name of the target column in the internal table. - Either `csvColumnName` or `csvColumnIndex` to define the corresponding column in the CSV. - `containsHeader`: A boolean indicating whether the CSV includes a header row. #### Examples With column names: ``` { "mappings": [ { "name": "numcol", "csvColumnName": "numcol" }, { "name": "text", "csvColumnName": "text" }, { "name": "decimalcol", "csvColumnName": "decimalcol" } ], "containsHeader": true } ``` With column indexes: ``` { "mappings": [ { "name": "numcol", "csvC	`projectId`,`tableName`	Not stated