Menu
Read-only reference for the Syndly MCP API. Use when an agent hits an MCP error or wants to know what tools are available and how to call them.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Draft a post from a capture using your brand voice profile and the target platform voice.
First-run onboarding. Scaffold ./.syndly/ at the project root and write your brand voice profile plus per-platform tones.
Show news captures that have arrived since your last check.
List the current post queue and its status.
List, create, edit, and remove content sources that Syndly uses to discover news captures.
Summarise recent post performance with recommendations.
| name | syndly-help |
| description | Read-only reference for the Syndly MCP API. Use when an agent hits an MCP error or wants to know what tools are available and how to call them. |
Read-only discovery and error-interpretation helper for the Syndly MCP API. Surfaces the live tool surface, lists the user's projects/sources/posts on demand, and interprets common MCP errors.
tools/list once per session../.syndly/.Read ./.syndly/brand-voice.md and ./.syndly/platforms/*.md so the skill knows the project's voice setup before answering. If those files are missing, the skill still works but its answers won't be tailored to the project.
tools/list (live MCP). If it fails, surface the error verbatim and stop — the user needs to fix auth first.list_projects to confirm which project slug(s) the API key has access to. Do not assume — the user may not know which project their key is bound to.tools/list)./.syndly/brand-voice.md)./.syndly/platforms/*.md)create_post: required fields (project_slug, account_id, content, type), the confirmed: true gate on mutating tools.list_projects / list_sources / list_posts as appropriate. Use the project slug from step 3.tools/list again and report../.syndly/brand-voice.md.The MCP server has known limitations that affect what this skill can answer:
| Error message | What it means | Recovery |
|---|---|---|
Missing Authorization header | SYNDLY_API_KEY (or SYN_MCP_KEY) is not in the agent's env | Set the env var; hint file at ./.syndly/README.md documents where it lives |
Invalid API key | Token is wrong, expired, or revoked | Regenerate the key in the Syndly web UI |
Project not found | Slug typo or project was deleted | Call list_projects to discover valid slugs |
Project does not belong to this API key | The API key is bound to a different project than the one in project_slug | The user can only see the project their key is bound to. To work with a different project they own via the web UI, they need to generate a new API key scoped to that project. (Tracked as Syndly issue #1497.) |
list_projects returns only projects the API key is bound to. Web-UI ownership is invisible from MCP. (Tracked as Syndly issue #1497.)add_source, create_post, schedule_post, publish_now, cancel_post, remove_from_queue, disconnect_channel, update_project_settings all require confirmed: true in their input schema. This is enforced by Zod (z.literal(true)), so the call fails server-side if missing.add_source, create_post, schedule_post, publish_now, cancel_post, remove_from_queue, disconnect_channel, update_project_settings, remove_source) belong in their dedicated skills (/syndly-sources, /syndly-draft, /syndly-queue).tools/list connectivity check. If it fails, every subsequent call will fail for the same reason.