# One set of endpoints (https://sellersheetai.com/docs/mcp-api)

> The same tools, with the same arguments and the same results, for your AI over MCP, for your code over the Tool API, and behind the Google Sheets add-on.



SellerSheet has one set of tools — more than <Count name="tools" floor="100" /> of them. They reach you three ways, each with its own job:

1. **An MCP tool** your AI calls in a conversation — through `https://sellersheetai.com/mcp`. This is where the work happens: your agent reads, decides, asks you, and acts. [Connect an AI client](/docs/start/clients).
2. **A Tool API operation** your own code calls — `POST https://api.sellersheetai.com/api/v1/tools/{tool}`. A dashboard or approval page your agent builds on it is live: its numbers update and its buttons act on Amazon. Early access — [Call from code](/docs/mcp-api/code).
3. **The engine behind the Google Sheets add-on**, where your team does bulk edits and keeps the record. See the [add-on docs](/help/sheets).

Over MCP and the Tool API a tool keeps its name, its arguments and its result, so a call your agent made in chat, your code can make tomorrow (the add-on drives the same operations from your sheet rows):

<ToolCall tool="orders_searchOrders" args="{ created_after: &#x22;2026-10-01T00:00:00Z&#x22; }" />

## What every call shares [#what-every-call-shares]

* **One store argument.** Store-scoped tools take `store`, a ref such as <StoreRef /> from `get_user_context` — [Store refs](/docs/mcp-api/store-refs).
* **One result shape.** `notification`, `data`, `human_action` — [Responses & errors](/docs/mcp-api/responses).
* **One way to page.** A token in, a token out; your agent or your loop calls again — [Paging](/docs/mcp-api/paging).
* **One label per tool.** Read, write or destructive, and write access per store — [Read, write & destructive](/docs/mcp-api/access).
* **The vendor's own names.** A tool that wraps one Amazon operation carries Amazon's name, such as `orders_getOrder` or `fbaInbound_listPlacementOptions`; a SellerSheet workflow over several operations keeps the API area's prefix with a lower-case tail, such as `fbaInbound_create_sta_sheet`.
* **The schema says the rules.** Allowed values, bounds and formats from Amazon's specification are in each tool's input schema, so a wrong value is refused before anything reaches Amazon.

## Where to go next [#where-to-go-next]

* [Workflows](/docs/mcp-api/workflows) — one page per job, FBA first.
* [Tool reference](/docs/mcp-api/tools) — every tool, its arguments and a ready call.