
Creative Constraints MCP server
online · 100% uptimecreative-constraints — an original deck of 162 domain-neutral creative constraints, drawn by…
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Creative Constraints yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Creative Constraints tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Creative Constraints compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 333 ms
- faster than 44% of 30,031 servers
Release history: 4 versions in the registry since 2026-10-22, latest 2026-10-31, typically one every 4 days.
Install Creative Constraints in Claude Code, Cursor or VS Code
claude mcp add --transport http creative-constraints https://gateway.pipeworx.io/creative-constraints/mcp
What the publisher says
From the Creative Constraints repository's README, as published. We do not edit it. Read it on GitHub
@pipeworx/creative-constraints
Draws from an original, 162-card deck of domain-neutral creative constraints — each card is one imperative sentence an agent or a team can apply to any task (a product launch, an essay, an onboarding flow, a dinner), plus one sentence on why it helps. Meanings are returned separately from interpretation: the tool hands back what was drawn and the procedure used, and the calling agent decides what to do with it.
Part of Pipeworx — an MCP gateway connecting AI agents to 1866+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Part of the Pipeworx "chance" family — a shared seeded-RNG and session engine also used by dice-roller, tarot, i-ching and random-tables (see docs/chance-packs-plan.md).
Tools
cards, optionally restricted to one or more of the nine categories. Pass seed to reproduce an exact draw later (same seed + count + categories always returns the same cards); omit it for a fresh random draw, and the seed actually used is returned. Pass session_id from a previous response to continue a no-repeat session (draw-without-replacement across calls).
- drawconstraint(count?, categories?, seed?, sessionid?) — draws 1-10
card count and one example title.
- listconstraintcategories() — lists the nine categories, each with its
"inversion_03").
- get_constraint(id) — fetches one specific card by its id (e.g.
Auth
Keyless. No upstream API, no third-party dependency.
Data sources
constraint sentence and rationale is written for this pack; there is no public-domain or commercial foundation behind it (unlike tarot's Rider–Waite–Smith tradition or i-ching's Legge translation).
- Pipeworx — original creative-constraints deck. Every card's title,
The nine categories
perspective, limitation, medium, time, audience, inversion, scale, process, wildcard — 18 cards each, 162 total.
Sessions are hosted-only
drawconstraint's sessionid support depends on the gateway's KV cache binding (injectCacheKv: true on this pack's manifest row). The published npm standalone has no such binding, so a sessionid there (or from any caller without the gateway's cache) gets sessionsupported: false in the response and falls back to a plain seeded draw — fully reproducible by seed, just not draw-without-replacement across separate calls. Sessions expire after 24 hours of inactivity.
Reproducibility
Every draw is seeded. Omit seed for a fresh random draw (the seed used is always returned in meta.seed); pass that seed back, with the same count and categories, to reproduce the exact same cards. When continuing an existing session via session_id, the session keeps the category filter it was opened with — categories is ignored on that call.
Errors
An unknown category in categories is a loud error listing the valid set. An unknown id to getconstraint is a loud error with the id-naming convention. An expired or unknown sessionid is a loud error telling you to omit it to start a new session.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"creative-constraints": {
"url": "https://gateway.pipeworx.io/creative-constraints/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/creative-constraints/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Creative Constraints: common questions
- Is Creative Constraints MCP server safe?
- Mostly: it is graded B (77/100). Read the Creative Constraints safety report
- How do I install Creative Constraints?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Creative Constraints need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Creative Constraints maintained?
- The last commit was 13 days ago (2026-10-22). The latest release is v0.2.1.
- Is Creative Constraints up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Creative Constraints compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 333 ms (faster than 44% of 30,031 servers). Full comparison.