IndiaNIC releases Byline publishing tool as open source under MIT licence

The MCP server publishes to Ghost and WordPress and ships documented platform behaviour from live testing.

· 3 min read
a reporter at a desk reviewing notes beside a laptop in a busy open office
In short
IndiaNIC has released Byline, an MIT-licensed MCP server that drafts and publishes articles to Ghost and WordPress, under an open-source licence.
  • Released: August 3, 2026, at github.com/indianic/byline.
  • Scope: Ghost and WordPress, running locally with no hosted component.
  • Measured: WordPress publishes a scheduled post immediately at 45 seconds of lead time; 60 seconds schedules correctly.
  • Licence: MIT, with the platform behaviour documented in the repository.

AHMEDABAD, August 3 — IndiaNIC released Byline, a publishing tool that connects AI assistants directly to Ghost and WordPress blogs, as open-source software on Sunday, publishing the full source under an MIT licence at github.com/indianic/byline.

The tool is an MCP server, a program that runs on a user's own machine and exposes a defined set of actions to an AI assistant. Byline exposes 14, covering research, drafting, image generation, scoring and publishing, according to the project documentation, which builds on the Ghost Admin API and the WordPress REST API.

It carries no hosted component and no user account. Credentials are read from a local file and sent only to the blog and image services the user configures, the repository states.

an empty desk at night with a monitor glowing and a half-finished mug beside it
The difference is rarely in the grammar.

Platform behaviour documented from live testing

The release includes reference documents recording how Ghost and WordPress respond to publishing requests, each entry traceable to a request made against a live installation rather than to platform documentation.

One finding concerns scheduling. WordPress does not reject a scheduled post whose publication time is too close to the present, according to the project's measurements published in the repository. It changes the status from "future" to "publish", returns a success code, and the article goes live immediately with no error in the response.

Measured against WordPress's own server clock, a lead time of 45 seconds published the article at once, while 60 seconds scheduled it correctly, the documentation states. Ghost returns a 422 error for the same request and writes nothing.

The same documents record that a publish request carrying a future date produces opposite results on the two platforms: Ghost publishes the article immediately while retaining the future date, and WordPress schedules it. Byline refuses that combination rather than sending it, and reads each post back after writing to confirm what the platform stored.

Aimed at structural markers of generated text

The project states that its writing brief targets structural characteristics of machine-generated prose rather than vocabulary alone, naming uniform paragraph length, consistently parallel lists and arguments that avoid taking a position.

Byline varies the opening, structure, narrative angle and prose texture for each article, and varies how prominently the author's credentials appear. In roughly 60% of articles the author's role and years of experience are not stated at all, according to figures published with the release.

The documentation does not claim the output evades AI-detection software. "That claim could not be verified from inside this codebase," the project's engineering rules state, adding that unverifiable claims are excluded from the tool's own descriptions.

Refusals built into the publishing path

Several behaviours are refusals rather than features. The tool declines to publish an article with no images unless the caller states explicitly that the article has none, declines a scheduled time under two minutes ahead, and declines to combine results from two research providers into one article.

The stated design rule is that no operation fails silently: every action returns either a result or an error naming the API and its HTTP status, and every write is compared against a read-back of what the platform stored.

Availability

Byline requires Node 20 or newer and a Ghost or WordPress blog the user can publish to. It supports Claude Code, Cursor, Windsurf, Gemini CLI and Codex, and any other MCP-capable tool through a manual configuration step, the documentation states.

The project does not currently publish to social platforms or generate video. Adding a destination requires one folder and one registry entry, according to the repository's extension guide.

Frequently asked questions

What licence is Byline released under?

MIT. The full source, the platform reference documents and the engineering rules are published in the repository at github.com/indianic/byline, and the licence permits commercial use, modification and redistribution.

Does Byline require a subscription or an account?

No. The tool runs on the user's own machine with no hosted component and no account. Users supply their own blog credentials and, optionally, their own image and research API keys.

Which platforms does it publish to?

Ghost and WordPress. The repository states that adding a further platform requires one folder and one registry line, and documents the verification a new platform must pass before it is trusted.