CreationLoop MCP Server

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.

• Endpoint: https://creationloop.ai/api/mcp
• Transport: Streamable HTTP (stateless, JSON responses)
• Authentication: none required
• Method: POST only (JSON-RPC 2.0)

What the server is

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.

Transport details

The server implements the MCP Streamable HTTP transport in stateless mode:

• URL: https://creationloop.ai/api/mcp
• Accepted method: POST with a JSON-RPC 2.0 body.
• Response mode: plain JSON (application/json). The server runs with JSON responses enabled and no SSE stream, so each request gets a single JSON reply.
• Sessions: none. Every request builds a fresh server and transport pair, so there is no session id to track and no session to resume or delete.
• 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.
• Server identity: name creationloop, version 0.1.0.

Rate limits

Limits are per client IP, on a fixed 60 second window:

• All MCP traffic: up to 30 requests per minute. Over the limit, the server replies with HTTP 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).

Tool reference

The server exposes four tools.

get_company_overview

• Input: none. Schema is an object with no properties (additionalProperties: false).
• Output: a single text block. What CreationLoop is, how the content loop works, the two run modes, proof, philosophy, and the pricing stance, served verbatim from CreationLoop's canonical site copy.

get_design_partner_offer

• Input: none. Schema is an object with no properties (additionalProperties: false).
• Output: a single text block describing the design-partner program: what partners get, what CreationLoop asks in return, and how to apply. Served verbatim from the canonical site copy.

get_faq

• Input: none. Schema is an object with no properties (additionalProperties: false).
• Output: a single text block of frequently asked questions and answers, served verbatim from the canonical site copy.

submit_design_partner_application

Submits 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) | |-----------|--------|----------|---------

... View full README on GitHub