Cursor

Connect Cursor to staqly as an MCP server, and Cursor's agent can create collections, write posts with media and a text per channel, and put them on the calendar. Do this once per machine (~/.cursor/mcp.json) or once per repository (.cursor/mcp.json).

Connect to Staqly Community EditionCopy Anchor Link

export STAQLY_API_KEY=$(staqly serve token)   # Docker: $(docker exec staqly server token)

mkdir -p .cursor && staqly mcp config cursor --snippet > .cursor/mcp.json

{
  "mcpServers": {
    "staqly": {
      "url": "http://localhost:3333/mcp",
      "headers": { "Authorization": "Bearer ${env:STAQLY_API_KEY}" }
    }
  }
}

STDIO (Docker only)Copy Anchor Link

If you run staqly with Docker, you can use STDIO instead of HTTP. It runs mcp-stdio inside the staqly container, so it needs no token, and it does not work with staqly serve:

{
  "mcpServers": {
    "staqly": { "type": "stdio", "command": "docker", "args": ["exec", "-i", "staqly", "mcp-stdio"] }
  }
}

Connect to Staqly CloudCopy Anchor Link

Create a key for Cursor under Integrations → API keys, e.g. with collections:read posts:read posts:write media:write, export it, and reference it from the config. Cursor expands ${env:STAQLY_API_KEY}, so the key stays out of the file:

export STAQLY_API_KEY=stk_...
staqly mcp config cursor --snippet > .cursor/mcp.json   # with a cloud CLI profile

{
  "mcpServers": {
    "staqly": {
      "url": "https://app.staqly.ai/mcp",
      "headers": { "Authorization": "Bearer ${env:STAQLY_API_KEY}" }
    }
  }
}

Cursor reads the variable from the environment it was started in, so start it from that shell (cursor .) or set the variable for your login session.

Write posts, not just codeCopy Anchor Link

Add a project rule so the agent drafts into staqly instead of pasting text for you to copy:

---
description: Write posts into staqly instead of posting directly
alwaysApply: true
---

When asked for a social post, announcement or release note, write it into staqly:

1. Call `list_channels` once to know the channels and their limits, and `list_collections`
   for the collection names.
2. Call `create_post` with the collection, the text, one target per channel the post is for,
   and a shorter `content` on a target whose platform allows fewer characters.
3. Call `preview_post` and fix what a platform objects to; then `schedule_post` if a time was
   given, otherwise leave it as a draft for the collection's schedule.
4. When `list_requested_work` shows a schedule asking for posts, write three drafts into its
   collection in the voice of the previous ones.

The posts show up on the staqly calendar, and on your phone if you connected it. The full pattern is in Let an agent fill a collection.

Try itCopy Anchor Link

Ask in Cursor's agent chat:

"Create a collection called Release notes and draft a post about this week's changes for my X channel." "What is scheduled this week?"

More in Example prompts.

Next stepsCopy Anchor Link