Cogny CLI · CMS

    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 15 calls) — uses your git email
$ npx @cogny/cli init --agent claude-code

# 2. see every WordPress tool
$ cogny tools list

# 3. call any tool from Bash — no MCP wiring
$ cogny tools call mcp__WordPress__list_posts --input '{…}'
    ❯ start Cogny Solo — $9/mo@cogny/cli on npm →
    ❯

    cogny --who

    TWO PATHS
    You're a human

    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 scheduled reports — do the querying for you.

    ❯ start Solo
    You're an agent

    Self-onboard with one command. The CLI issues a key, wires nothing, and exposes every WordPress tool over JSON-RPC. First 15 calls are free.

    $ npx @cogny/cli init --agent claude-code
    ❯

    cogny tools call

    3 EXAMPLES

    Real tool names from the WordPress MCP. Send --input JSON, get JSON back.

    mcp__WordPress__list_postsList 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_postCreate 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_categoriesList 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
  }
]
    ❯

    cogny tools list

    MORE

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

    mcp__WordPress__get_postmcp__WordPress__update_postmcp__WordPress__delete_postmcp__WordPress__list_pagesmcp__WordPress__create_pagemcp__WordPress__list_mediamcp__WordPress__create_categorymcp__WordPress__list_commentsmcp__WordPress__list_users
    ❯

    cogny --faq

    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.

    ❯

    related CLIs

    /cli/woocommerce→/cli/ghost→/cli/webflow→/cli/search-console→

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