Creatif Space MCP server
Commit Nov 14, 2026Draft, send approval links, and publish social media content directly from your AI chat.
Also known as creatifren/creatif.space-api, creatif-space
- Stars
- 0
- Tools
- 1
- Downloads, 30 days
- —
- Latest version
- 1.2.1
- Last commit
- Nov 14, 2026
- License
- —
What is Creatif Space MCP?
Creatif Space is an MCP server. Draft, send approval links, and publish social media content directly from your AI chat. It exposes 1 tool, such as get_post.
Summary generated from the project's README
About Creatif Space MCP server
Managing social media content and client approvals from within an AI chat is what Creatif Space enables. This remote MCP server acts as a thin layer connecting your AI client to the Creatif Space V1 API, allowing you to draft posts, schedule content, and manage social channels without leaving your conversation. It is designed for social media managers and agencies who need to maintain a clear approval workflow between creators and clients.
Users connect by adding the remote connector URL to their client, such as Claude, and signing in to authorize access. The server uses your existing bearer tokens to ensure that all ownership, credits, and validation remain within the core platform. You can use specific tools like plan_week to generate drafts, send_for_approval to create client review links, or weekly_results to generate performance summaries. Every action that modifies content, such as schedule_posts or publish_post, requires a confirmation step to ensure nothing is posted without your explicit permission.
What you can do with it
- 1Drafting weekly social media contentGenerate a series of Instagram posts for an upcoming product launch as drafts.
- 2Managing client approval workflowsCreate a dedicated link for a client to review and approve pending social media drafts.
- 3Generating client performance reportsProduce a summary of the past month's social media results to share with a stakeholder.
- 4Monitoring account health and limitsCheck your current plan, remaining credits, and any social channels that need reconnection.
Written from the project's README. Every use case is checked against a quote from it.
How to install Creatif Space MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Creatif Space MCP in Claude Code
$ claude mcp add --transport http creatif-space https://mcp.creatif.space/mcpInstall Creatif Space MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"creatif-space": {
"url": "https://mcp.creatif.space/mcp"
}
}
}Install Creatif Space MCP in VS Code
.vscode/mcp.json
{
"servers": {
"creatif-space": {
"type": "http",
"url": "https://mcp.creatif.space/mcp"
}
}
}Install Creatif Space MCP in VS Code CLI
$ code --add-mcp '{"name":"creatif-space","type":"http","url":"https://mcp.creatif.space/mcp"}'Install Creatif Space MCP in Codex
$ codex mcp add creatif-space --url https://mcp.creatif.space/mcpInstall Creatif Space MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.creatif-space] url = "https://mcp.creatif.space/mcp"
Install Creatif Space MCP in Gemini CLI
$ gemini mcp add -s user --transport http creatif-space https://mcp.creatif.space/mcpInstall Creatif Space MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"creatif-space": {
"url": "https://mcp.creatif.space/mcp",
"type": "http"
}
}
}Creatif Space MCP tools 1
Detected from the READMEget_post
| get_post | — |
Configuration
MCP_AUTH_MODE
| Name | Description | |
|---|---|---|
| MCP_AUTH_MODE | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecreatifren/creatif.space-api is public and reachablegithub.com/creatifren/creatif.space-api ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/creatifren/creatif.space-api ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model1 tool description and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubcreatif.space MCP server
Remote MCP server for creatif.space. Connector
URL: https://mcp.creatif.space/mcp (also answers on /). Streamable HTTP, stateless, Node 22,
official @modelcontextprotocol/sdk.
It is a thin layer: every tool calls the existing V1 API with the caller's own bearer token, so ownership, plans, Credits and validation stay in Laravel. No business logic lives here.
Try it in 60 seconds (Claude)
- In Claude, open Settings → Connectors → Add custom connector, name it
creatif.spaceand paste the connector URL:https://mcp.creatif.space/mcp - Click Connect, sign in to creatif.space and allow access. Claude now sees your channels, drafts and approval links. Nothing is posted without your OK: every send shows a preview first.
- Ask one of these — each runs a ready-made prompt (also in Claude’s
prompts menu):
- “Plan next week: 5 Instagram posts about our winter launch.” →
plan_weekdrafts the posts on your channel. Drafts only, nothing goes out. - “Send my drafts to rani@client.com for approval.” →
send_for_approvalmakes an approval link for your client to approve or ask for changes. - “How did this week go? Give me a link for my client.” →
weekly_resultssums up the last 7 days and makes a link anyone can open. - “Make last month’s report for my client.” →
monthly_reportsums up a whole month, with the same kind of link.
- “Plan next week: 5 Instagram posts about our winter launch.” →
Endpoints
| Path | What |
|---|---|
POST /mcp (and POST /) |
MCP JSON-RPC (bearer required) |
GET /health |
Liveness, no auth: {ok, name, version} — the same version as serverInfo (from package.json; see CHANGELOG.md) |
GET /.well-known/glama.json |
Glama connector claim, no auth (also HEAD); same document at GET /mcp/.well-known/glama.json |
GET /.well-known/oauth-protected-resource |
RFC 9728 metadata: resource: "https://mcp.creatif.space/mcp", authorization_servers: ["https://api.creatif.space"] |
GET /.well-known/oauth-protected-resource/mcp |
the same document at the RFC 9728 path form |
POST /free |
Creatif Space Free Tools — a separate MCP server, no auth, 30 calls/min per IP |
CORS (browser clients: MCP Inspector web, web IDEs) on /mcp, / and
/free: OPTIONS → 204 with Access-Control-Allow-Origin: * (no
credentials — auth is the Bearer header only), Allow-Methods: GET, POST, DELETE, OPTIONS, Allow-Headers: authorization, content-type, mcp-protocol-version, mcp-session-id, last-event-id, Expose-Headers: mcp-session-id, www-authenticate, Max-Age: 600. The same headers are on
every response from those paths, 401 and 429 included. Done in the Node app
(src/cors.ts); nginx passes OPTIONS through and must not add its own
Access-Control-* headers.
No / invalid token → 401 with
WWW-Authenticate: Bearer resource_metadata="https://mcp.creatif.space/.well-known/oauth-protected-resource/mcp" (RFC 9728 path form, built from the origin; the root well-known serves the same document).
Auth
Tokens (Passport OAuth 2.1 access tokens or cs_live_… API keys) are checked with
POST {V1_API_URL}/oauth/introspect, header X-MCP-Secret, body {token} →
{active, user_ulid, scopes[], client_id, client_name, token_type, exp}.
Answers are cached 60 s (never past exp). The same bearer is then forwarded
to V1 routes (guard mcp, built in the OAuth PR).
Scopes (scopes_supported): read, draft, approve, publish, approvals:decide — the same
names as config/mcp.php on the API. Every V1 call carries X-MCP-Tool and
X-MCP-Client for the API's audit log (never content).
Rate limit: 60 requests / minute / token (429 + Retry-After).
Clients get a client_id either by Dynamic Client Registration
(POST /oauth/register) or with an OAuth Client ID Metadata Document:
the client_id is an https URL serving {client_id, client_name, redirect_uris, token_endpoint_auth_method: "none"}. The API fetches it
(public addresses only, no redirects, ≤ 5 KB, cached per Cache-Control
5 min–24 h) and advertises client_id_metadata_document_supported: true.
Tools
| Tool | Scope | V1 endpoint |
|---|---|---|
list_channels — channels that need reconnecting carry reconnect {reason, next_step} and are listed in needs_reconnect |
read | GET /social-accounts |
list_posts (status: draft, waiting, changes_requested, scheduled, published, failed, cancelled; from/to as a date or time; channel_id, limit) — waiting / changes_requested read status=scheduled and keep posts by approval |
read | GET /social-posts?status&from&to&account_id&limit |
list_failed_posts (limit, cursor) — last 30 days, per channel failure_code + reason; partly-published posts list only their failed channels |
read | GET /social-posts?status=failed + ?status=published (from/to = last 30 days) |
get_post |
read | GET /social-posts/{id} |
list_files (search, type, folder_id, limit) |
read | GET /files |
draft_post (caption, channel_ids, file_ids, media_urls, captions_by_channel, type) |
draft | POST /social-posts with draft: true |
get_account_summary — onboarding in one call: plan, limits used/left, Credits left, channels connected / needing reconnect, storage used, failed_posts (last 30 days), approvals {waiting, changes_requested}, next_steps |
read | GET /credits, GET /social-accounts, GET /files/usage, GET /social-posts?status=failed + ?status=published (as list_failed_posts), GET /social-posts?status=scheduled |
get_onboarding — the “Get started” checklist (connect, draft, send, publish), each {done, at}, plus next {step, tool, suggest}: the one next step to suggest |
read | GET /me/onboarding |
get_credits — plan, limits, Credits; spend (this cycle by action: publish, reply, ai) and renewal (resets_at, days_until) |
read | GET /credits (limits.spend) |
create_approval_link (post_ids — or a Content Plan: date_from, date_to, timezone, channel_ids — approver_email (required — the client signs in with it to decide), title, client_name, expires_in_hours) — every plan; Free: one client (by approver_email), 7-day window, 10 queued |
approve | POST /social-approval-links (drafts accepted) |
create_content_plan (date_from, date_to, timezone, channel_ids, approver_email, title, client_name, expires_in_hours, confirm) — preview first; confirm: true creates the Content Plan and emails the approver |
approve | GET /social-accounts, GET /social-posts?from&to (preview); confirm: true → POST /social-approval-links with notify_approver: true |
check_approval_status (post_id | link_id) |
read | GET /social-posts/{id} or GET /social-approval-links/{id} |
send_approval_reminder (link_id) |
approve | POST /social-approval-links/{id}/remind (one per link per 12 h) |
update_post (caption, scheduled_at, labels, file_ids | add_file_ids) |
draft (drafts and posts waiting for approval only) | PATCH /social-posts/{id} |
schedule_posts (posts: [{post_id, scheduled_at}] up to 10, confirm) — one preview of every post + total Credits; confirm: true schedules all or none |
publish | previews GET /social-posts/{id}/send-preview each; confirm: true → POST /social-posts/send-batch (checks all first; a refusal takes back the ones already sent) |
schedule_post (post_id, scheduled_at, confirm) |
publish | preview GET /social-posts/{id}/send-preview; confirm: true → POST /social-posts/{id}/send |
publish_post (post_id, confirm) |
publish | same, sends now |
retry_post (post_id, confirm) — the failed channels of a post again; preview shows each failure_code and reason |
publish | preview GET /social-posts/{id}/retry-preview; confirm: true → POST /social-posts/{id}/retry |
get_insight_summary (period: {month} | {from, to} ≤ 92 days, channel_ids) — Pro / Max; Free → plan_required |
read | GET /insight/summary?month | from&to&channel_ids |
list_top_posts (period: {month} | {from, to} ≤ 92 days, channel_ids, limit, cursor) — Pro / Max; Free → plan_required |
read | GET /insight/top-posts?month | from&to&channel_ids |
get_best_times (days 7–92, channel_ids) — Pro / Max; Free → plan_required |
read | GET /insight/best-times?days&channel_ids |
get_insight_csv_link (from, to ≤ 366 days, channel_ids) — Pro / Max; Free → plan_required |
read | POST /insight/export-csv-link |
get_insight_report_link (from, to ≤ 92 days, format onepage|deck|details, channel_ids, locale) — a 15-minute signed download link to the Insight PDF (one page, 16:9 deck or detailed); Pro / Max |
read | POST /insight/export-link |
create_insight_share_link (from, to ≤ 92 days, channel_ids, recipient_email) — a read-only web link to an Insight report, open without an account for 30 days; with recipient_email that person is emailed once and sees it in list_shared_with_me |
approve | POST /insight/share |
revoke_insight_share_link (share_id) — turns a shared Insight link off at once |
approve | DELETE /insight/share/{id} |
request_media_upload (filename, mime, size_bytes, folder_id) |
draft | POST /files/presign → file_id + presigned PUT URL (15 min) |
confirm_media_upload (file_id) |
draft | POST /files/{id}/complete (409 → GET /files/{id}: already ready is returned) |
list_conversations (type comment|dm, channel_id, unread_only, since, limit, cursor) — Engage comments and DMs in one list, newest first |
read | GET /inbox/feed?type&account&unread&since&per_page&cursor |
reply_to_conversation (conversation_id, text, confirm) — DM into the thread, or public reply under a comment |
publish | preview GET /inbox/feed/{id}; confirm: true → POST /inbox/feed/{id}/reply |
get_storage_usage — used vs quota (Free: 1 GB total; paid: Keep quota) and kept vs auto-delete (soonest dates), from the newest 300 files |
read | GET /files/usage + GET /files?per_page=60&page=1..5 |
keep_file (file_id) — Pro/Max; Free → plan_required, quota full → storage_full, not ready (409) → file_not_ready |
draft | POST /files/{id}/keep |
unkeep_file (file_id) — back under the retention rules; returns auto_delete_at |
draft | DELETE /files/{id}/keep |
discard_draft (post_id, confirm) — deletes a draft only; preview first, confirm: true deletes; scheduled / published / failed → not_draft with the next step |
draft | GET /social-posts/{id}, then DELETE /social-posts/{id}/draft |
list_approval_links (status active|expired|revoked|all, limit) — status, approver email, post count, approved/waiting/revision |
read | GET /social-approval-links |
revoke_approval_link (link_id, confirm) — preview, then revokes the link for good; unanswered posts come back to the user |
approve | GET then DELETE /social-approval-links/{id} |
list_waiting_approvals — posts other users sent to this user for approval |
approvals:decide | GET /me/approvals/waiting |
decide_approval (link, post_id, decision approve|revise, reason, confirm) — the approver side; same rules as the approval page, audited as mcp |
approvals:decide | preview GET /me/approvals/{post}/preview; confirm: true → POST /me/approvals/{post}/decision |
list_spaces (status draft|published|archived, search, limit) — Pro/Max |
read | GET /spaces?tab&search |
create_space_from_files (title, file_ids 1–100, view_mode) — always a Draft+Private Space, never published; Pro/Max |
draft | POST /spaces with file_ids (checked before anything is created) |
publish_space (space_id, confirm) — Pro/Max |
publish | preview GET /spaces/{id}/publish-preview; confirm: true → POST /spaces/{id}/publish |
get_approval_history (post_id) — every decision on one post, oldest first: who (email masked), when, decision, comment |
read | GET /social-posts/{id}/approval-audit |
get_plan_calendar_link (link_id) — ICS feed URL of a Content Plan (scheduled posts, first 60 characters of the caption); read-only, stable URL |
read | GET /social-approval-links/{id}/calendar |
get_approval_audit (link_id) — every decision on one of the user's links: who, post, when, decision, comment; rows and CSV |
read | GET /social-approval-links/{id}/audit.csv |
send_feedback (kind bug|idea|other, message, page) — to the creatif.space team; nothing public, no Credits; 10 an hour per user |
draft | POST /feedback |
get_notification_settings — which emails the user gets: post_missed_or_failed (“Post missed / failed”; the publish_failed switch unless the API serves its own key), approval_decided, weekly_digest |
read | GET /me/notification-settings |
update_notification_settings (post_missed_or_failed — or its older name publish_failed —, approval_decided, weekly_digest: true/false; timezone of the Monday 08:00 digest; at least one) |
draft | PATCH /me/notification-settings |
list_shared_with_me — "Reports shared with you": Content Plans and Insight reports other users shared with this user's email |
approvals:decide | GET /me/reports/shared |
get_connect_link (network) — the app's connect page (https://creatif.space/social/connect?network=…) with the steps; no token in the response; a new network on a full plan → plan_required |
read | GET /social-accounts + GET /credits (never POST /social-accounts/auth-url) |
Media upload. request_media_upload → the client PUTs the exact bytes to
the URL (Content-Type and Content-Length are signed) → confirm_media_upload
→ the id goes in draft_post / update_post file_ids. Same presign and
complete as the app, so every rule stays in Laravel: Free 1 GB total, Pro 25 GB
/ Max 50 GB Keep quota, per-file caps, accepted formats, magic-byte check.
Refusals come back as storage_full (free-up-space files_url + billing_url
upgrade link), file_too_large, unsupported_format, upload_limit,
upload_incomplete (confirm before the PUT), file_not_ready (an unconfirmed
or foreign id in a post); another workspace's id is not_found.
schedule_post / publish_post without confirm: true only return a preview
(channels, Credit cost, sends left today, anything blocking). Sends from a bearer
token are capped at 20 per user per UTC day, enforced in Laravel
(CapTokenSends, 429 daily_send_cap); the app's cookie session is never capped.
confirm_token. The send preview returns a confirm_token signed by the API
(HMAC with the app key; bound to user + post + target ids + Credit price; valid
10 minutes). A send from a bearer token (MCP guard or API key) must bring it
back: none → 422 confirm_token_required; mismatched, expired or forged → 409
preview_stale. Holding a draft for approval and the app's cookie session need
none. This server keeps the token of the last preview per user + post in memory
and sends it on confirm: true — the model never sees it. No preview on record
(never shown, expired, already used, server restarted) → a fresh preview and
nothing sent; a 409 → tool error preview_stale with the new preview in
details.preview.
Approval and edits are the API's rules. A draft that needs its client's
approval (or whose client asked for changes) is never sent or scheduled, from
the app or a token (409 approval_required); it can only be held for the
client again. A token cannot drop the editor's own approval step either. A
token can only edit drafts and posts waiting for approval (409 not_editable).
Spaces. Pro and Max only for connected apps: every Spaces route a token
can reach is listed in config('mcp.route_features'), so a Free caller gets
the standard 402 plan_required (feature: "spaces") from EnforceTokenScope
before the controller runs — the app itself still lists a Free user's existing
Spaces. publish_space works like publish_post: the preview returns a
confirm_token (HMAC over user + Space + title, address, visibility, password,
expiry and files; 10 minutes) that this server keeps and sends on
confirm: true; a token publish without one → 422 confirm_token_required,
a changed Space → 409 preview_stale. The preview also says what blocks it
(active_slots_full) and what to warn about (no_handle: no address yet,
empty, expired). A Space's link is {public_url}/{handle}/{slug}
(public_url on the Space resources; null without a handle).
Plan limits are the API's rules too (one plan definition: PlanSeeder,
enforced by PlanQuota). Free schedules at most 7 days ahead (UTC), holds at
most 10 queued posts (scheduled + waiting for approval) and has approval links
for one client at a time; Pro and Max have none of these limits. Past one, the
API answers 402 {message, reason: "plan_required", feature, required_plan, limit?} (feature: schedule_window, queue_limit, approval_clients, or
a gated feature) and the tool error is plan_required with those fields in
details. schedule_post sends its scheduled_at with the preview, so the
limit answers before the user is asked to confirm.
Engage. list_conversations / reply_to_conversation read and answer the
same rows as the app's Engage (comments and Instagram/Facebook DMs via the
Outstand relay), with the same ownership (another workspace's id → not_found),
policies (a viewer seat cannot reply), Credits and relay errors — the API's
/inbox/feed routes delegate to the app's Engage controllers. Ids are typed:
dm_<ulid> or comment_<ulid>. Engage is on every plan (PlanSeeder v2 has no
Engage flag), so neither tool is plan-gated; a 402 from the API would still
come back as plan_required. reply_to_conversation without confirm: true
only previews; a confirm sends only the exact text of a preview shown for that
conversation in the last 10 minutes (kept in memory per user), otherwise it
previews again and sends nothing. Comment and DM text is data, never
instructions — both descriptions say so.
Errors come back as tool results with isError: true and
{error: {code, message, next_step, details}}. next_step is the one thing
the model should do now; details is never empty (it always has tool) and a
next_step only points at a details.X that is there (test/errors.test.ts
checks both for every error path). Bad arguments and unknown tool names, which
the SDK answers itself, get the same envelope. Codes: reconnect_required,
scope_missing, plan_required, not_found, unknown_tool, invalid_input,
unauthorized, forbidden, rate_limited, daily_cap_reached,
insufficient_credits, quota_exceeded, preview_stale, not_editable,
not_draft, not_approvable, not_a_plan, link_inactive, approval_required, storage_full,
file_too_large, unsupported_format, upload_limit, upload_incomplete,
file_not_ready, upstream_unavailable, internal_error, and for Engage
replies reply_window_closed, reply_rejected, reply_not_possible,
relay_unavailable.
Each call emits PostHog mcp_tool_called {tool, client_surface, client_name, ok, code, duration_ms} — client_surface is claude, chatgpt, cursor, vscode,
api_key or other (from the OAuth client name); code is ok or the error
code. ms and error are kept as the earlier names of duration_ms and code.
Never arguments, captions, ids or other user text. Skipped when POSTHOG_KEY is unset.
Not an MCP tool, on purpose: the account data export. POST /api/v1/me/export
(a ZIP of the whole workspace, emailed as a 24-hour link) works only from a
signed-in creatif.space session. It is not in mcp.routes, so an OAuth or API
token gets 403. A full copy of an account is not something to hand an AI
client.
Approve from your AI chat
For the client — the person a creatif.space user sent posts or a Content
Plan to for approval. They connect creatif.space to Claude or ChatGPT with
their own account (the email the link was sent to), allow Decide approvals
(approvals:decide) on the consent screen, and can then review and decide
without opening the approval page.
| Tool | What it does |
|---|---|
list_shared_with_me |
"Reports shared with you": Content Plans and Insight reports shared with the user's verified email — title, dates, who sent it, link (and, for plans, how many posts wait). |
list_waiting_approvals |
Every post still waiting on the user's decision, with the link id and post id to decide with. |
decide_approval |
Approve, or request changes with a reason. Always shows a preview first; decides only with confirm: true after the user agrees. |
The owner's side has two more (scope read): get_approval_audit — who
decided what and when, with the comment, as rows and CSV, for one of the
owner's own links — and get_approval_history — the same for one post,
across every link it was on, with the approver's email masked.
Rules the tools keep (the API enforces them; the tools only explain them):
- Only links addressed to the user's verified email. Anyone else gets
forbiddenwith a hint of the expected address; an id from another workspace isnot_found. - Two steps for every decision: preview, then confirm. The confirm carries a
signed token (10 minutes) over the exact post the user saw; if the post was
edited in between, the answer is
preview_stalewith the new preview and nothing is decided. The token never reaches the model. - Same rules as the approval page: the post must be in the plan's dates and
channels and still waiting; on a Free sender's plan only the next 7 days
can be decided (
invalid_inputwithdecidable_from). - Every decision is audited with
source: mcp, and the sender is notified exactly as from the page. - A day before the first waiting post goes out, the approver gets one
reminder email (once per plan; they can turn it off from the email, or the
owner with
PATCH /social-approval-links/{id}{reminders: false}).
Example conversation
Rani: Anything I need to approve this week?
Claude calls
list_shared_with_meandlist_waiting_approvals.Claude: Bro shared one Content Plan with you, December (1–31 Dec, Asia/Jakarta). Two posts are waiting for you:
- "Launch day — 20% off everything…" — Instagram, Wed 2 Dec 09:00
- "Behind the scenes at the studio" — Instagram, Fri 4 Dec 18:00
Rani: Approve the first one. For the second, ask them to use the photo with the team in it.
Claude calls
decide_approvalwithdecision: "approve"for post 1 anddecision: "revise",reason: "Please use the photo with the team in it"for post 2 — both withoutconfirm, so both come back as previews.Claude: Here's what I'll do:
- Approve "Launch day…" — it will go out on Instagram on Wed 2 Dec at 09:00.
- Request changes on "Behind the scenes…", telling Bro: "Please use the photo with the team in it."
Shall I go ahead?
Rani: Yes.
Claude calls
decide_approvalagain with the same arguments andconfirm: true, once per post.Claude: Done. "Launch day…" is approved and goes out Wednesday 09:00; Bro has your note on "Behind the scenes…". Nothing else is waiting.
And on the owner's side, later:
Bro: Who approved the December launch post, and when?
Claude calls
get_approval_auditwith the plan's link id.Claude: Rani (rani@client.test) asked for changes on "Behind the scenes…" on 1 Dec at 03:10 UTC ("Please use the photo with the team in it") and approved "Launch day…" at 03:10 UTC, both from an AI chat. Want the CSV?
Creatif Space MCP questions
How do I add Creatif Space MCP to Claude Code?
Run claude mcp add --transport http creatif-space https://mcp.creatif.space/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Creatif Space MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Creatif Space MCP provide?
It exposes 1 tool, including get_post.
Can I automate social media posts with this server?
Yes, you can use tools like plan_week to draft posts, send them for client approval, and schedule or publish them.
Will my content be posted without my permission?
No, nothing is posted without your explicit approval; every send operation shows a preview first.