Set up Simplified
Connect Simplified where you already work. Each guide covers that platform’s setup, sign-in, workflow skills, verification, and common problems.
Choose your platform
For terminal scripts, use CLI installation. For direct integrations, start with API authentication.
Let your assistant help
In a local assistant that can read documentation and configure its own environment, paste:
Your assistant should open the matching platform guide above and follow the verification checklist. You complete sign-in when prompted. In hosted chat, it can guide you through the app’s settings; it cannot configure your computer by installing into a cloud sandbox.
What you are setting up
MCP supplies tools and authentication. Skills supply instructions for combining those tools into campaigns, content production, and other workflows. A plugin may package both; otherwise the platform guide covers them separately.
The hosted MCP endpoint is https://apikit.simplified.com/mcp. Available capabilities depend on your connection and client permissions. After setup, verify your workspace and tools, then try the first-draft walkthrough.
Instructions for the assistant
When the user asks you to use this document to set up Simplified, carry out the applicable setup steps instead of only summarizing them. Follow your host’s permissions and the user’s requested scope. Installing or updating client configuration is part of setup; creating content, publishing, and paid generation are not setup tests.
1. Identify the client and execution environment
Use the current session’s platform information to distinguish Codex, Claude Code, Claude chat, Cursor, and ChatGPT. Do not infer the client solely from a CLI executable found on the machine. If the platform is genuinely unclear, ask which client the user wants configured.
Determine whether you can configure that client on the user’s computer. A hosted chat terminal or sandbox is not the user’s computer. In a hosted client, guide the user through the supported plugin or connector settings rather than installing local packages in the sandbox.
2. Read the relevant platform guide
Fetch the matching Markdown document before choosing commands or editing configuration:
Also read the verification checklist. If a guide cannot be retrieved, try its normal page by removing .md. If neither is accessible, report the missing guide rather than guessing installation commands.
3. Inspect and complete only what is missing
Check the tools and skills available in this session and the relevant client’s existing configuration. Reuse a working Simplified plugin or connection. Do not add a standalone MCP server alongside a plugin that already provides it.
Follow the platform guide for plugin installation, MCP connection, and skills. For ChatGPT, start with the Simplified plugin listing; custom MCP creation is an advanced alternative. Check local prerequisites and command help before running an installer. Preserve unrelated configuration and honor project-only or user-wide scope. Do not install into other clients just because they are present.
The Simplified CLI is optional for MCP setup. Install it only if the user also wants terminal workflows. Installing skills alone does not establish a connection, and a configured connection does not prove skills are available.
4. Complete sign-in and load the connection
Use the platform’s supported sign-in flow. Let the user complete authentication when interaction is required. Do not request passwords, API keys, or OAuth tokens in chat or print stored credentials.
If the client needs a reload or a new session to discover installed tools, say what was configured and give the next action. Use “configured; verification pending” until tool calls can actually run. On resuming, check the existing setup before installing again.
5. Verify access without changing workspace data
Discover the actual tool names; the client may add a prefix. Call api_getWorkspaceInfo and api_listTeamspaces. Report the returned workspace and accessible teamspaces. If the user named a teamspace, resolve it to its numeric ID. If no destination was specified, list the choices and leave selection pending rather than choosing the first one.
Check Simplified skill availability separately. Inspect the tools actually exposed before claiming support for workflows, agents, PM boards, or any other capability. Do not generate media, create a project, schedule a post, or spend credits to prove setup works.
6. Return a clear setup result
Finish with a short report using these fields:
- Client and scope: which client and installation scope were configured.
- Connection: verified, configured but awaiting reload/sign-in, or blocked with the specific reason.
- Workspace: the name and ID returned by the identity tool, or “not verified.”
- Teamspace: the resolved destination, or “not selected” with available choices.
- Skills: available, installed but awaiting reload, not installed, or unsupported by this client.
- Next action: the one remaining user step, or a suggested first task if setup is verified.
A successful installer exit is not proof that the connection works. If setup is partly complete, preserve that progress and explain exactly what remains.