Partnerloop

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

CreationLoop design partners: company overview, partner offer, FAQ, and apply.

VerifiedSTDIODesktop only

Server details

Identifier: io.github.CloudCorpRecords/partnerloop
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Nov 3, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account CloudCorpRecords for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.CloudCorpRecords%2Fpartnerloop.svg)](https://sourceweft.com/mcp/io.github.CloudCorpRecords%2Fpartnerloop?utm_source=readme&utm_medium=badge)

Overview

Partnerloop's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

Open Partnerloop in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

partnerloop

partnerloop connects to CreationLoop's hosted MCP endpoint and exposes its public design-partner surface: the canonical company overview, the design-partner program offer, the FAQ, and a way to submit a design-partner application. One binary serves a command-line interface and a stdio MCP server; both simply forward each call upstream, so the text you get back is CreationLoop's own canonical copy, never a local paraphrase.

No API key or account is needed. The endpoint can be overridden with CREATIONLOOP_MCP_URL; when it is not set, calls go to https://creationloop.ai/api/mcp.

Install

Or run the container image:

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

bash

partnerloop overviewpartnerloop offerpartnerloop faqpartnerloop apply --email [email protected] --website https://example.com \  --name Ada --company Example --message "Scaling content."
partnerloop --version

partnerloop overviewpartnerloop offerpartnerloop faqpartnerloop apply --email [email protected] --website https://example.com \  --name Ada --company Example --message "Scaling content."
partnerloop --version

The three read commands print the upstream text exactly as the hosted server returns it. apply prints the upstream confirmation. Exit codes: 0 on success, 1 when a call fails (a validation problem, an upstream error, or a rate limit), 2 for usage errors.

Applications are checked locally before anything is sent: email (a valid address, 3–320 characters) and website (1–500 characters) are required; name and company may be up to 200 characters each and message up to 2000. Unknown fields are rejected. A failed check exits 1 with the problem named, and no request is made.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

MCP client configuration:

json

{  "mcpServers": {    "partnerloop": {      "command": "npx",      "args": ["-y", "@reneturcios/partnerloop", "mcp"]    }  }}

{  "mcpServers": {    "partnerloop": {      "command": "npx",      "args": ["-y", "@reneturcios/partnerloop", "mcp"]    }  }}

To point the server at a different CreationLoop-compatible host, add CREATIONLOOP_MCP_URL to the client's env for this server.

Tools

Tool	Input	What it returns
`get_company_overview`	(none)	CreationLoop's canonical company information, verbatim from upstream.
`get_design_partner_offer`	(none)	The design-partner program description, verbatim from upstream.
`get_faq`	(none)	Frequently asked questions and answers, verbatim from upstream.
`submit_design_partner_application`	`email`, `website` (required); `name`, `company`, `message` (optional)	The upstream confirmation that the application was received.

Upstream errors — including the endpoint's rate limits (30 requests/minute overall, 5 submissions/minute for applications) — come back as error results carrying the upstream message.

Development

bash

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Source: README.md at commit 511052f

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts