Back to Browse

Partnerloop MCP Server

Developer ToolsModerate6.3MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

6.3
Moderate6.3Moderate Risk

partnerloop is a small, transparent forwarder that sends four fixed JSON-RPC tools/call requests to CreationLoop's hosted endpoint and requires no credentials. Local validation runs before the design-partner application is submitted, and the code shows no exfiltration, shell execution, or hardcoded secrets. Remaining concerns are low: the endpoint can be redirected via an environment variable, which would route applicant personal data to any host that variable names, and the upstream fetch has no explicit timeout. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub 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

npx @reneturcios/partnerloop overview

Or run the container image:

docker run -i ghcr.io/cloudcorprecords/partnerloop

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

CLI

partnerloop overview
partnerloop offer
partnerloop faq
partnerloop apply --email founder@example.com --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:

npx -y @reneturcios/partnerloop mcp

MCP client configuration:

{
  "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

ToolInputWhat 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_applicationemail, 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

npm install
npm 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.

Reviews

No reviews yet

Be the first to review this server!