# Retool: products, MCP servers and connect URLs, one vendor page

> Retool (retool.com): 1 product in The GTM MCP Directory, 1 with an official MCP server, 0 answering a live handshake, 50 tools catalogued. Data baked 2026-09-27.

*Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).*

*Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.*

---
[Directory](../index.md) /
[Vendors](../vendors/index.md) /
Retool

# Retool

1 product in the directory
1 official MCP server
0 live handshakes
Data baked 2026-09-27

Vendor domain: [retool.com](https://retool.com) · vendor page id retool-com

**The rollup**

- **Products**: 1, facts checked by hand 2026-09-07

- **Official MCP servers**: 1 of 1, as recorded on 2026-09-07

- **Community MCP servers**: 0 of 1

- **Live handshake**: 0 of 1 answered an MCP initialize, 1 probed, 2026-09-04

- **Repo local**: 0 of 1: a server you install and run yourself

- **Docs only**: 1 of 1: the recorded URL is a page about the server, not the server

- **Tools catalogued**: 50 named across 1 measured server, harvested 2026-09-27

- **Bench tested**: 0 of 1 here, 1 of 1,252 across the directory

- **Ships a CLI**: 1 of 1 official, 0 community only, 0 none found, harvested 2026-09-27

- **GitHub organisation**: [github.com/tryretool](https://github.com/tryretool), tied to the domain with evidence 2026-09-08

A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.

**Products, 1**

### [Retool](../tools/retool.md)

A low-code platform for building internal tools/dashboards/admin panels on top of databases and APIs; in a GTM context, used to build custom RevOps tooling - lead-routing consoles, deal-desk approval apps, data-correction UIs - on top of the warehouse/CRM.

[Official MCP](../mcp/official.md) · [Free to start](../gates/free.md)
[RevOps Infra](../categories/revops-infra.md)
RESEARCHED

- **Endpoint probe**: docs page, not an endpoint, 2026-09-04

- **Connect URL**: [https://retool.com/blog/retool-mcp-server](https://retool.com/blog/retool-mcp-server) (docs page)

- **Tools catalogued**: 50 named, harvested 2026-09-27, catalogue fixed

- **last_checked**: 2026-09-07

**The gates, in plain words**

1 of 1 free to start, a solo operator gets API access without talking to anyone.

The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.

**Jobs the vendor says its products do**

- [Query a data warehouse](../jobs/query-data-warehouse.md)
- [Run an automation workflow](../jobs/run-automation-workflow.md)

2 distinct job labels, the union across 1 product, tagged 2026-08-25. A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

**Connect URLs**

- [https://retool.com/blog/retool-mcp-server](https://retool.com/blog/retool-mcp-server) (Retool, docs page, probed 2026-09-04)

An endpoint is where an agent connects. A docs page is where a person reads about connecting. Both are published because both are what the probe found; an agent needs the first.

**Command line**

### [Retool](../tools/retool.md) retool official CLI

```
npm install -g @tryretool/cli
```

quoted from [https://www.npmjs.com/package/@tryretool/cli](https://www.npmjs.com/package/@tryretool/cli) on 2026-09-27, via npm

harvested 2026-09-27, all on the [tool page](../tools/retool.md).

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.

**On GitHub**

[github.com/tryretool](https://github.com/tryretool) tied to the vendor by rule 3, account website https://retool.com has the vendor's domain, confidence strong

- **Public repositories**: 41, forks excluded, as read on 2026-09-08
- **Mention MCP**: 0 of them
- **Look like CLIs**: 1 of them
- **Latest push**: 2026-09-08

The five most recently pushed, on 2026-09-08:

| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| [agent-plugins](https://github.com/tryretool/agent-plugins) | plugin or integration | | 0 | 2026-09-08 | |
| [terraform-provider-retool](https://github.com/tryretool/terraform-provider-retool) | infrastructure | | 4 | 2026-09-04 | v2.1.0 |
| [legal](https://github.com/tryretool/legal) | other | Retool Legal Agreements and Policies | 1 | 2026-09-04 | |
| [terraform-retool-self-hosted-blueprints](https://github.com/tryretool/terraform-retool-self-hosted-blueprints) | infrastructure | Terraform modules to deploy self-hosted Retool to your cloud | 5 | 2026-09-03 | v0.3.5 |
| [retool-helm](https://github.com/tryretool/retool-helm) | infrastructure | | 54 | 2026-09-03 | v6.11.23 |

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

**What this page does not claim**

A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another.

Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).
