Other MCP clients
1. Check client support
Your client needs remote HTTP MCP support and either OAuth or a supported way to supply an authorization header. Inspect its connection settings and tool list first; reuse a working Simplified entry.
2. Add the endpoint
Create a remote server entry named Simplified with:
Use the client’s own configuration format. A JSON file written for Cursor or another client is not automatically valid everywhere.
3. Authenticate
Complete OAuth if supported. Otherwise, create a key in Simplified API settings and use the client’s secure credential mechanism to supply:
Do not send the placeholder as a real credential. See MCP authentication for account and teamspace scope.
4. Add workflow instructions if supported
If the client supports skills, follow its supported installation process for the Simplified skills repository. Otherwise use the workflow guides as reference material. Be explicit about whether instructions are persistent or available only in the current chat.
Verify the connection
Start a new conversation if the client has not loaded the new tools. Ask:
Use Simplified to identify my connected workspace and list its teamspaces. Do not create or change anything.
The assistant should call api_getWorkspaceInfo and api_listTeamspaces, then report the workspace and available teamspaces. Choose the intended teamspace before starting work. A saved server entry or a successful skills installation alone does not verify tool access.
Next, follow the MCP quickstart to prepare a social draft. For a read-only first task, ask the assistant to list your brand kits. Social accounts are only needed for social tasks; an empty account list does not mean the connection failed.
Troubleshooting
If the client cannot complete remote authentication, inspect the exact error and its documented transport requirements. Do not change the endpoint to a guessed URL or disable security checks. Use one of the dedicated platform guides if your client is listed there.
For file workflows, check whether the client can read and upload bytes. Remote MCP alone does not give the server access to your local filesystem; see Assets and uploads.