cogny clicmsfirst 15 calls free

    wordpress scriptable from Bash.

    List and write WordPress posts, pages, categories, tags, media and users, and read comments — from the shell over the WordPress REST API MCP. Content ops without wp-admin or a wp-cli SSH session.

    • 1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
    • 2. see every WordPress toolcogny tools list
    • 3. call any tool from bash, no MCP wiringcogny tools call mcp__WordPress__list_posts --input '{…}'
    01two paths
    you're a person

    Managing a WordPress site means logging into wp-admin and editing posts one at a time. The CLI lets an agent create, update, and categorize posts in bulk and pull your content as JSON. Connect WordPress once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

    Start Solo
    you're an agent

    Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every WordPress tool over JSON-RPC. The first 15 calls are free.

    • npx @cogny/cli init --agent claude-code
    02tools call

    real WordPress tools.

    Tool names as the WordPress MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

    • mcp__WordPress__list_posts

      List posts with status filtering.

      • cogny tools call mcp__WordPress__list_posts \ --input '{"per_page":2,"status":"publish"}'
      example response
      [
        {
          "id": 5012,
          "title": {
            "rendered": "AI-native analytics"
          },
          "slug": "ai-native-analytics",
          "status": "publish",
          "date": "2026-06-12T09:00:00"
        },
        {
          "id": 5009,
          "title": {
            "rendered": "From dashboards to prompts"
          },
          "slug": "dashboards-to-prompts",
          "status": "publish",
          "date": "2026-06-05T09:00:00"
        }
      ]
    • mcp__WordPress__create_post

      Create a draft post with categories.

      • cogny tools call mcp__WordPress__create_post \ --input '{"title":"CLI for content teams","content":"<p>Draft body…</p>","status":"draft","categories":[7]}'
      example response
      {
        "id": 5051,
        "slug": "cli-for-content-teams",
        "status": "draft",
        "link": "https://blog.acme.com/?p=5051"
      }
    • mcp__WordPress__list_categories

      List taxonomy terms with post counts.

      • cogny tools call mcp__WordPress__list_categories \ --input '{"per_page":3}'
      example response
      [
        {
          "id": 7,
          "name": "Product",
          "slug": "product",
          "count": 42
        },
        {
          "id": 9,
          "name": "Engineering",
          "slug": "engineering",
          "count": 31
        },
        {
          "id": 11,
          "name": "Marketing",
          "slug": "marketing",
          "count": 18
        }
      ]
    03tools list

    the rest of the surface.

    A sample of the other WordPress tools. Run cogny tools list --json for every tool and its input schema.

    • mcp__WordPress__get_post
    • mcp__WordPress__update_post
    • mcp__WordPress__delete_post
    • mcp__WordPress__list_pages
    • mcp__WordPress__create_page
    • mcp__WordPress__list_media
    • mcp__WordPress__create_category
    • mcp__WordPress__list_comments
    • mcp__WordPress__list_users
    04then a verdict

    calls from a script. verdicts from cogny.

    Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

    • worked

      Moved the number. Every measured win has a share card.

    • partial

      Some of it did.

    • didn't work

      On the record anyway, so it isn't proposed again.

    • inconclusive

      Not enough data to call.

    How the loop works

    05questions

    questions.

    How is this different from wp-cli?
    wp-cli runs over SSH on the server. This is the Cogny CLI calling the WordPress REST API MCP over the cogny-mcp-proxy — no shell access to the host needed, just an application password or OAuth connected once in Cogny.
    Can it manage media and taxonomy too?
    Yes. Beyond posts and pages it exposes `list_media`, `list_categories` / `create_category`, `list_tags` / `create_tag`, and user tools — the common content-ops surface, all returning JSON.
    Can my coding agent use it without MCP setup?
    Yes. `npx @cogny/cli init` issues a key, then `cogny tools call mcp__WordPress__create_post --input ...` runs from any shell — no /mcp wiring or restart.
    06related

    Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

    wordpress, then a verdict.