Company
About GoBuildWP. Built close to WordPress, checked against the source.
GoBuildWP is a self-hosted WordPress MCP plugin: your site runs its own MCP server, and calls are checked against site policy and WordPress permissions. This page explains the source checks, evidence limits and correction process. A content hash or successful website check does not establish that a human reviewed every product claim.
Who maintains it
The GoBuildWP team
The GoBuildWP team maintains the plugin and writes and reviews the technical content on this website, published under the company name. Reviews trace capability, pricing, setup, safety, integration and SEO statements to the current product source or a cited primary source.
The code is public: you can read it before you install it.
Evidence standard
Say what is real. Name what still needs proof.
A source-backed capability, a passing build, a successful tool response and a production-ready workflow are different kinds of evidence. Pages keep them apart.
What we can verify in the product
- 89 current Pro source modules and 91 integration requirement guides; these are different count units
- 27 named AI clients and their connection routes
- Declared WordPress and PHP requirements
- Registered ability groups and input schemas
- Server-side safety profiles and policy checks
- Licence and dependency gates in source
What still needs live validation on your site
- A specific third-party plugin version on a real site
- Authenticated browser and native-editor behaviour
- Production caches, security layers, email and external providers
- Physical-device and representative responsive review
- Provider-side money, fulfilment, translation or delivery outcomes
- Your team's permission, backup, approval and recovery process
Content method
How a GoBuildWP page is reviewed
The goal is an answer a person, a search engine or an AI system can use without losing its operating boundary.
Trace the product
Inspect the current Free abilities, Pro modules, client registry, readme requirements and licence behaviour.
Map one intent
Give each page a distinct question instead of creating several pages for trivial keyword variations.
Write the limitation
State dependencies, permissions, safety controls, staging needs and external checks next to the capability.
Structure the answer
A direct introduction, semantic headings, examples, FAQ, breadcrumbs and accurate structured data.
Verify the page
Run lint and builds, audit routes and metadata, inspect responsive layouts and measure performance.
Re-review when facts change
Update pages when GoBuildWP, WordPress, AI clients, companion plugins or official guidance changes.
How we check claims
Where each statement on this site comes from
Pages are written and maintained by GoBuildWP, the company, which is the name on every byline.
Generated facts and curated references are checked separately
Versions, source module declarations, client choices and count snapshots are exported from source. The ability reference remains curated, with checks for names, editions, explicit static annotations and selected evaluated contracts. Passing those checks does not verify every description, permission callback or runtime effect.
Third-party facts carry a source and a date
What a vendor plugin stores, how an AI client is configured and what a competing server offers are taken from that vendor's own documentation, linked on the page with the date it was checked. Where a vendor page could not be read, the page says so instead of guessing.
Examples say what they are
A worked sequence of abilities is labelled as a representative run from the reference unless it is a dated test result.
No invented proof
No ratings, review markup or usage statistics are published. Customer quotes appear only when real, approved submissions with consent exist.
Dates describe their evidence
"Content updated" records when a page's own text changed, using a fingerprint of that text. It is not a human review date. Articles retain their original publication and editorial review dates; an automated source correction does not advance those dates. A deploy or design change alone does not establish a new review.
Accuracy and corrections
Found something that needs another look?
Send the URL, product version, what you observed and any reproducible evidence. We would rather correct a claim than defend stale copy. Security reports have their own route on the security page.
The product and the company
About GoBuildWP: what the company actually ships
About GoBuildWP in one sentence: it is a WordPress plugin that turns a site into its own MCP server, plus a paid add-on and an optional hosted service. Each piece can be judged separately, and each has a different relationship with your data and your money.
- GoBuildWP Free is the foundation. It is GPL-licensed, its source is public on GitHub, and it registers its tools through the WordPress Abilities API and serves them with the MCP Adapter package published by the WordPress project, bundled into the release ZIP. It works on its own, with no account and no payment.
- GoBuildWP Pro adds integrations for the page builders, form plugins, SEO plugins, custom-field frameworks and other tools a site already runs, along with skills, persistent agent memory and a human approval queue. It loads an integration only when the plugin it drives is installed. Without a licence that Freemius accepts, it loads only its activation and licence screens and two safety settings an owner may have switched on, the write-approval hold and the fresh-backup gate.
- GoBuildWP Cloud, at app.gobuildwp.com, is an optional gateway that lets one AI app reach several sites through a single sign-in. It is free for a small number of sites and has no separate price; a Pro licence raises its limits.
- This website, gobuildwp.com, carries the documentation and the changelog, and answers the update checks both plugins make, because neither is distributed through WordPress.org.
Who makes GoBuildWP, and how it is paid for
GoBuildWP is built and maintained by the GoBuildWP team, which publishes under the company name. Both plugin headers name GoBuildWP as the author, and the bylines on this site do the same, so a page is the company's statement rather than one person's opinion. The contact page explains how to reach the engineers directly.
The business is funded by GoBuildWP Pro licences. Freemius sells them as merchant of record, which means Freemius takes the payment, charges any tax due and issues the licence, and GoBuildWP never handles card details. Every tier unlocks the same Pro plugin features, so nobody pays more to unlock one; tiers differ by how many sites may activate Pro and by the Cloud allowances that come with them, and the pricing page lists both. There is no paid services arm, no paid bug bounty and no hosted AI model to resell: the incentive is for the plugin to be worth a licence on the sites people already run.
Decisions you can verify in the code
Several choices shape how GoBuildWP behaves on a site, and each is visible in the public source rather than being a promise on a marketing page.
- A direct connection has no relay. The AI client talks to your site's own MCP endpoint, so tool calls never pass through GoBuildWP's servers unless you choose Cloud.
- Limits are enforced on the server. The safety profile, per-ability switches, confirmation rules and access-token ceilings are checked inside WordPress, so a client that ignores them still cannot get past them.
- Abilities are tied to a hostname. A clone or migration of the site comes up with its abilities switched off until an administrator turns them on at the new address.
- Activation respects an earlier no. The first activation switches AI Abilities on, but a site that has turned them off keeps that decision through every reactivation.
- The Pro licence check fails closed where it cannot decide. A missing or broken Freemius SDK, or a build without its licensing identifiers, counts as unlicensed. Otherwise Pro takes the answer of the Freemius SDK, which reads the licence stored on the site and re-syncs it in the background, rather than keeping a second rule of its own.
- Uninstalling cleans up after itself without deleting your work. Plugin tables and options go; code you wrote through the sandbox and saved designs stay unless you opt in to removing them.
What GoBuildWP does not do
GoBuildWP does not include, host or choose an AI model. The client you connect brings its own, and the in-dashboard Chat uses whichever provider you configure through the WordPress AI Client. GoBuildWP does not ask for access to your site to provide support, and its diagnostics and audits are configuration checks, not a malware scanner or a penetration test. Those boundaries are written into the terms and the privacy page as well as here, so the three pages cannot quietly disagree.
When the product changes, the version numbers shown on this site come from the plugin source rather than being typed by hand, and the changelog records what each release added, fixed or removed.
FAQ
How the claims here are made
Who writes the pages on this site?
The GoBuildWP team maintains the plugin and its technical content, and publishes under the company name. AI-assisted drafts and code checks are part of the workflow. Article bylines and review dates come from their editorial records; an automated check is not a human review.
How do you decide what counts as a verified claim?
Registration and schemas are evidence of an implemented code path. They do not show that a task completed on an installed site. We distinguish source checks, automated harness tests, vendor documentation and dated runtime tests. Third-party versions, editor behavior, cache layers, mail and payment-provider effects need separate verification.
How often is this reviewed?
Pages are re-reviewed when the thing they describe changes: a GoBuildWP release, a WordPress release that moves a requirement, a companion plugin that renames a capability, or an AI client that changes how it is configured. The ability reference is curated. A source check flags missing literal registrations and Free abilities listed only as Pro; it does not prove every description or dependency correct.
What happens if I find something wrong?
Send the URL, the product version and what you actually saw. We would rather correct a claim than defend it, and include a reproduction if possible. We can then compare it with the documented behavior.
Start in Read Only. Expand when it has earned it.
Install the free plugin, connect your AI client, and see exactly what it can reach before it changes anything.