The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Creationloop listing page.
CreationLoop is your Marketing Agent.
Verified agent output. The recursive loop that gets better, and proves it.
This is the public listing for CreationLoop's remote MCP server. The server lets any MCP-capable agent read CreationLoop's canonical company information and submit a design-partner application on a user's behalf. It is a hosted, remote server: there is nothing to install and no key to configure. Point your client at the endpoint below and connect.
https://creationloop.ai/api/mcpPOST only (JSON-RPC 2.0)CreationLoop is a Marketing Agent for early-stage founders and small brands. The MCP server exposes a small, deterministic surface: three read tools that return CreationLoop's canonical public copy verbatim, and one write tool that submits a design-partner application. No model sits in the response path of the read tools, so their output is fixed text, not generated on the fly.
The server is remote and hosted by CreationLoop. Your client connects over Streamable HTTP; there is no local process, no package to install, and no credential to supply.
The server implements the MCP Streamable HTTP transport in stateless mode:
https://creationloop.ai/api/mcpPOST with a JSON-RPC 2.0 body.application/json). The server runs with JSON
responses enabled and no SSE stream, so each request gets a single JSON reply.GET and DELETE: return HTTP 405 with a JSON-RPC error
(code -32000, message "Method not allowed. POST JSON-RPC to this endpoint.").
Because the server is stateless there is no SSE stream to open on GET and no
session to remove on DELETE.creationloop, version 0.1.0.Limits are per client IP, on a fixed 60 second window:
429 and a JSON-RPC error (code -32000, message
"Too many requests. Try again shortly.").submit_design_partner_application: a tighter 5 submissions per minute.
Over the limit, the tool returns a tool result flagged as an error with the
text "Too many requests. Try again shortly." (the JSON-RPC call itself
succeeds; the error is carried in the tool result).The server exposes four tools.
get_company_overviewadditionalProperties: false).get_design_partner_offeradditionalProperties: false).get_faqadditionalProperties: false).submit_design_partner_applicationSubmits an application to CreationLoop's design-partner program. The founder reviews every application and follows up by email.
Input schema (strict; unknown fields are rejected):
| Field | Type | Required | Constraints | Server field description (verbatim) |
|---|---|---|---|---|
email | string | yes | valid email, 3 to 320 chars | "Applicant email address (required)." |
website | string | yes | 1 to 500 chars | "The brand's website URL (required)." |
name | string | no | up to 200 chars | "Applicant name (optional)." |
company | string | no | up to 200 chars | "Company name (optional)." |
message | string | no | up to 2000 chars | "What should your CMO know? Context for the email follow-up (optional)." |
The field descriptions above are the server's own text, reproduced verbatim so agents match the deployed contract exactly.
Output: a text confirmation. On success the message confirms the application was received for the brand's host and states that the founder reviews every application and follows up at the email provided. On invalid input the tool returns an error result naming the validation problem.
What is stored. A successful submission records a lead row with:
design-partner-mcp:{host}, where {host} is
the hostname derived from the website value (leading www. stripped), with
the whole source string capped at 64 characters;What is not stored. The raw website URL is not persisted; only the derived
hostname survives, inside the source string. The requester's IP address is used
only for in-memory rate limiting and is not written to storage.
Idempotency and email. Submissions are idempotent on the email address: a duplicate email does not create a second row. Welcome and internal notification emails are sent only for a genuinely new signup. If persistence fails, the tool returns an error asking the applicant to email the founder directly instead.
The same hosted MCP endpoint can expose one additional advisory-only tool,
review_gtm_sweep, to an authenticated CreationLoop operator. The tool reviews
a ten-person creationcode prospect packet and returns recommendations. It cannot
approve, send, connect, comment, or perform any external action.
The Cursor/GrokBot plugin in this repository declares GTM_REVIEW_TOKEN as a
protected plugin variable. Cursor stores the value through its plugin
configuration surface and injects it into the HTTP MCP authorization header. Do
not place the token in chat, source code, mcp.json, a URL, or shell history.
To install:
https://github.com/marino129/creationloop-mcp into the plugin search.creationloop-gtm-review.GTM_REVIEW_TOKEN in the protected variable field.review_gtm_sweep; it does not grant the public application
submission tool or any execution capability.The repository contains only the ${GTM_REVIEW_TOKEN} placeholder. Secret
material remains outside Git.
The server is a remote Streamable HTTP MCP server with no authentication. Use the config block for your client.
Add the server from the command line:
Claude Desktop connects to remote Streamable HTTP servers through the mcp-remote
bridge. Add this to your claude_desktop_config.json:
If your version of Claude Desktop supports custom remote connectors directly, you
can instead add the endpoint URL https://creationloop.ai/api/mcp as a custom
connector with no authentication.
Add this to your Cursor MCP config (~/.cursor/mcp.json for a global entry, or
.cursor/mcp.json in a project):
Once connected, ask your client to list tools. You should see
get_company_overview, get_design_partner_offer, get_faq, and
submit_design_partner_application. A raw check with curl:
The contents of this listing repository (documentation and configuration) are released under the MIT License. See LICENSE.