Creationloop

What is Creationloop?

Creationloop is a remote MCP server that lets any MCP-capable agent read CreationLoop’s canonical company information and submit a design‑partner application on a user’s behalf. It is hosted and requires no installation or configuration.

How to use Creationloop?

Point your MCP client at the endpoint https://creationloop.ai/api/mcp using Streamable HTTP (POST, JSON‑RPC 2.0). No authentication is needed. Example configuration for Claude Code: claude mcp add --transport http creationloop https://creationloop.ai/api/mcp. For Claude Desktop or Cursor, add the endpoint in their respective config files.

Key features of Creationloop

• Remote, hosted server – nothing to install.
• No authentication required.
• Streamable HTTP transport with stateless JSON responses.
• Three read tools returning canonical copy verbatim.
• One write tool for submitting design‑partner applications.
• Rate limits per IP: 30 req/min (all), 5/min for applications.

Use cases of Creationloop

• An agent retrieves CreationLoop’s company overview, design‑partner offer, or FAQ.
• A user submits a design‑partner application through their agent.
• A developer verifies the server connection by listing tools.
• A brand’s founder or CMO obtains canonical marketing copy via their agent.

FAQ from Creationloop

What does Creationloop do?

Creationloop is a remote MCP server that exposes four tools: three read tools that return fixed, canonical text about CreationLoop (overview, design‑partner offer, FAQ) and one write tool that submits a design‑partner application.

How do I connect to the server?

Point your MCP client to https://creationloop.ai/api/mcp using POST with JSON‑RPC 2.0. No authentication is required. The server uses Streamable HTTP in stateless mode.

What runtime or dependencies are needed?

None. The server is hosted remotely. Your client only needs to support the MCP Streamable HTTP transport.

Where does submitted data live?

A successful application stores the applicant’s email (normalized), a derived source string, and optional name/company/message. The raw website URL is not stored; only the hostname is kept. The IP address is used only for rate limiting and is not persisted.

What are the rate limits?

All MCP traffic: 30 requests per minute per client IP. The submit_design_partner_application tool has a tighter limit of 5 submissions per minute. Exceeding limits returns HTTP 429 or a tool error.