The Cognee WordPress connector is an open feature proposal, not a confirmed released integration. The proposal describes a connector that would let users select WordPress content—initially posts, pages, and comments—and make it searchable through Cognee. Its implementation and availability should not be assumed from the issue alone.
What the Cognee proposal asks to build
The Cognee community issue, opened August 28, 2026, proposes a wordpress data-source connector in packages/connector/wordpress/, following the structure of existing community connectors. The issue page reviewed for this article does not show a linked development branch or pull request, so its details are proposed requirements rather than shipped behavior. See the Cognee WordPress connector issue.
As an Amazon Associate I earn from qualifying purchases.
The proposed first-pass scope is posts, pages, and comments, with configurable custom post types to accommodate sites that rely on plugins. Its acceptance criteria call for content selection, searchable ingestion, incremental updates, deletion handling, setup instructions, a runnable example, and tests covering ingestion and the incremental cursor. The issue summarizes its intended outcome as: “Selected content is ingested and searchable in cognee”—an acceptance criterion, not confirmation that the connector already works.
How WordPress content could flow into Cognee
WordPress exposes site resources through a REST API that returns JSON over HTTP. A connector would retrieve the resources the user selects, map them into content Cognee can accept, and send them through Cognee’s documented ingestion and processing APIs. Cognee documents POST /api/v1/add for text, documents, or structured data, POST /api/v1/cognify for transforming raw data into structured knowledge graphs, and POST /api/v1/search for semantic search. See the Cognee API reference.
That is the conceptual data path, not a verified implementation walkthrough: the reviewed documentation does not establish that a completed WordPress connector currently performs this end-to-end flow.
What the proposed sync behavior means
Choose the content to ingest
The proposal expects users to select the WordPress content they want in Cognee. Its baseline is posts, pages, and comments; configurable custom post types would extend coverage to sites whose plugins register additional content types. The issue does not specify a final configuration screen or a completed selection workflow.
Authorize access with an Application Password
The proposal names WordPress Application Password authentication. The credentials must be authorized for the content scope being requested: public REST resources may be accessible differently from private or password-protected content, internal-user resources, custom post types, or metadata. WordPress documents these access considerations in its REST API Plugin Handbook. Whether a particular managed host or site configuration supports the needed access must be checked on that installation.
Fetch changes incrementally
Rather than re-ingesting everything on every run, the issue proposes a modified_after filter for incremental retrieval. In practice, a connector would need to track a cursor or timestamp and request eligible content changed since the previous sync. The issue includes tests for the incremental cursor among its acceptance criteria, but does not document a released cursor format or guarantee how edge cases are handled.
Propagate deletions
The proposal says that when source content has been deleted, it should be removed from Cognee’s graph on the next sync. This is a requirement for the planned behavior; the issue does not establish that deletion detection or graph cleanup is already implemented.
WordPress’s Connectors API is a different feature
WordPress 7.0 introduces its own Connectors API and a Settings → Connectors screen, initially aimed at registering external-service connections and AI providers. That framework is distinct from the Cognee community proposal: the latter is a data-source connector intended to read WordPress content into Cognee, not the WordPress settings framework itself. WordPress explains the 7.0 framework in its Connectors API announcement.
For credentials entered through the WordPress Connectors screen, WordPress documentation says API keys are masked in the interface but are not encrypted when stored in the database. Environment variables or PHP constants are alternatives for credential sources. This is a consideration for that WordPress feature; it should not be mistaken for instructions or behavior established for the proposed Cognee connector. See WordPress’s Settings Connectors screen documentation.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a Cognee runtime for the broader workflow
Cognee documents both its managed Cognee Cloud service and a local Docker setup. With a managed deployment, the service is hosted for you and uses its documented API-key configuration; with a local setup, the operator runs and maintains the service. These are documented deployment options, not alternatives compared in a performance or cost test. The Cognee API reference is the starting point for the currently documented API and deployment information.
Quick Recap
Best Value
- easy to use
- Free app
- Compatible with all devices
- It gives the best comparison between ten different hosts
What to verify before planning around it
- Check the Cognee issue for a linked implementation, pull request, release, or updated scope; the reviewed issue page did not show a linked branch or pull request.
- Confirm that your WordPress REST API exposes the particular content types and fields you intend to ingest, and that the account can access restricted resources.
- Confirm your site’s custom post types are exposed to the REST API if they need to be included.
- Use the current Cognee API documentation to confirm endpoint requirements and deployment setup before designing an integration around them.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
