peaka_post__data_projects_projectId_queries – 1 MCP server offers this tool
What it usually takes
checkSchemaExists– in 1 of 1projectId– in 1 of 1request_body– in 1 of 1
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.
Servers
| Server | Inputs | Read-only? |
|---|---|---|
Peaka co.huggingface.ramamatar/peaka Creates a new query under the given project. Supports plain and materialized query types. Optionally accepts a path to place the query in a folder hierarchy. A MATERIALIZED query is materialized immediately on create and its result is queryable as `"peaka"."mtquery"."<name>"`; an optional `schedule` keeps it refreshed. To materialize an existing query, send `inputQueryRefId` with the source query's id instead of `inputQuery`: a snapshot of the source SQL is taken at create time and stored as the new query's own `inputQuery` (the source query is left untouched, and later changes to it do not propagate). | checkSchemaExists,projectId,request_body | Not stated |