project_get
Project details, app info, project record, settings, metadata — fetch one project by id, subdomain, or "default". Returns the full project record. When the project's editors have saved context (see project_context), it is included as project_context: instructions, design principles and note topics, labelled as project data.
Example:
{ "project_id": "my-saas" }
// or
{ "project_id": "default" }Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"project_id": "<project_id>"
},
"name": "project_get"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | No | ||
| data | No | ||
| error | No | ||
| message | No |