> For the complete documentation index, see [llms.txt](https://docs.kinesis.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kinesis.network/mcp/tools.md).

# Tool reference

Every Kinesis MCP tool, with arguments, permissions and result schemas.

Select a resource family to find its tools. Each entry includes the exact tool name, arguments, JSON schemas, scopes, errors and corresponding REST operations.

| Reference                                                | Tools                                                                                                                                          |
| -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| [Identity and built-in docs](/mcp/tools/account-docs.md) | `whoami`, `read_docs`                                                                                                                          |
| [Projects](/mcp/tools/projects.md)                       | `list_projects`, `create_project`, `rename_project`, `delete_project`                                                                          |
| [Apps and templates](/mcp/tools/apps.md)                 | `list_apps`, `list_templates`, `get_app`, `create_app`, `update_app`                                                                           |
| [App lifecycle](/mcp/tools/lifecycle.md)                 | `get_app_status`, `start_app`, `stop_app`, `restart_app`, `delete_app`                                                                         |
| [Logs and usage](/mcp/tools/observability.md)            | `get_app_logs`, `get_app_usage`                                                                                                                |
| [Builds](/mcp/tools/builds.md)                           | `list_builds`, `get_build`, `get_build_logs`, `trigger_build`                                                                                  |
| [Custom domains](/mcp/tools/domains.md)                  | `manage_domain`                                                                                                                                |
| [GitHub](/mcp/tools/github.md)                           | `browse_github`                                                                                                                                |
| [Grids](/mcp/tools/grids.md)                             | `list_grids`, `create_grid`, `update_grid`, `delete_grid`                                                                                      |
| [Servers and orders](/mcp/tools/servers.md)              | `list_servers`, `provision_servers`, `deprovision_servers`, `power_servers`, `replace_server`, `get_provision_order`, `manage_provision_order` |
| [Catalog and marketplace](/mcp/tools/catalog.md)         | `browse_catalog`, `browse_marketplace`                                                                                                         |
| [Billing](/mcp/tools/billing.md)                         | `get_balance`, `get_costs`, `set_auto_reload`, `add_credits`                                                                                   |

## Before calling a tool

Use `whoami` to check the connected account. Discover project and app IDs from lists, grid IDs from `list_grids`, and server addresses from `list_servers`. Group filters can hide tools; scopes and resource roles determine whether a call is allowed.

The input schemas describe individual fields. Operation-level checks also enforce relationships between fields: a source selector can require additional arguments, a deployment must have a usable image or repository, and capacity and quota checks occur at runtime.

Successful calls return JSON in `structuredContent` and text content. A failed tool sets `isError: true` and returns an error envelope. Read [agent workflows](/mcp/workflows.md) for polling, retry and confirmation behavior.

REST additionally exposes single-project and single-grid detail reads, direct saved-card top-ups and top-up lookup. MCP groups domain, GitHub, catalog, power and order actions into compound tools. [REST API reference](/api.md) documents the full HTTP surface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kinesis.network/mcp/tools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.