# Loopio: products, MCP servers and connect URLs, one vendor page > Loopio (loopio.com): 1 product in The GTM MCP Directory, 0 with an official MCP server, 0 answering a live handshake, 16 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) / Loopio # Loopio 1 product in the directory 0 official MCP servers 0 live handshakes Data baked 2026-09-27 Vendor domain: [loopio.com](https://loopio.com) · vendor page id loopio-com **The rollup** - **Products**: 1, facts checked by hand 2026-09-02 - **Official MCP servers**: 0 of 1, as recorded on 2026-09-02 - **Community MCP servers**: 1 of 1 - **Live handshake**: 0 of 1 answered an MCP initialize, 1 probed, 2026-09-04 - **Repo local**: 1 of 1: a server you install and run yourself - **Docs only**: 0 of 1: the recorded URL is a page about the server, not the server - **Tools catalogued**: 16 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**: 0 of 1 official, 0 community only, 1 none found, harvested 2026-09-27 - **GitHub organisation**: none tied to loopio.com with evidence on 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** ### [Loopio](../tools/loopio.md) RFP/RFI response-management platform with a searchable content library, AI-assisted answer drafting, and collaborative proposal workflows for larger bid teams. [Community MCP](../mcp/community.md) · [Enterprise only](../gates/enterprise-only.md) [Proposals & Deals](../categories/proposals-deals.md) RESEARCHED - **Endpoint probe**: repo or package: install and run locally, 2026-09-04 - **Connect URL**: [https://github.com/fredericboyer/loopio-mcp](https://github.com/fredericboyer/loopio-mcp) (docs page) - **Tools catalogued**: 16 named, harvested 2026-09-27, catalogue fixed - **last_checked**: 2026-09-02 **The gates, in plain words** 1 of 1 enterprise only, API access needs a contract. 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** - [Draft an RFP or questionnaire response](../jobs/draft-rfp-response.md) 1 distinct job label, 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://github.com/fredericboyer/loopio-mcp](https://github.com/fredericboyer/loopio-mcp) (Loopio, 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** No CLI found for any product of this vendor by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **On GitHub** No GitHub organisation could be tied to loopio.com with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 6 candidate accounts seen and rejected by the evidence rules: fredericboyer, Loopio-EPD, Avnio, loopio-app, Loopio-AI. A name match alone is never accepted; the account has to point at the vendor domain. **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).