Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
The Cognee WordPress connector is currently described as an open feature proposal, not a released integration. The proposal calls for selecting WordPress content, ingesting it into Cognee, and making it searchable; the issue page reviewed for this article showed no linked development branch or pull request. Before planning around availability, check the Cognee issue for its current status.
What the proposed connector is meant to do
The Cognee project issue, opened August 28, 2026, proposes a wordpress connector in packages/connector/wordpress/ within cognee-community. Its initial content scope is posts, pages, and comments, with custom post types configurable for sites that rely on plugins to publish other kinds of content.
The issue’s acceptance criteria describe a target rather than confirmed product behavior: users should be able to choose content, ingest it so it is searchable in Cognee, update it incrementally, and handle deletions. The issue also asks for setup instructions, a runnable example, and tests covering ingestion and the incremental cursor.
How WordPress content could flow into Cognee
WordPress’s REST API provides site resources as JSON over HTTP. A connector would retrieve the resources permitted by the site, map selected items into content Cognee can accept, and send that material through Cognee’s documented ingestion and processing APIs. Cognee documents POST /api/v1/add for adding text, documents, or structured data, and POST /api/v1/cognify for transforming raw data into structured knowledge graphs. Semantic search is documented at POST /api/v1/search. See the Cognee API reference.
#1 Best Overall
That describes how the documented APIs fit together conceptually; it does not establish that a completed WordPress connector implements or has tested this end-to-end flow.
What the proposed sync needs to handle
Content selection
The proposal starts with posts, pages, and comments, and calls for configurable custom post types. This matters on plugin-heavy sites, where important content may not be represented as ordinary posts or pages. A useful setup would make the intended types explicit so that a sync does not silently omit content the site depends on.
Authentication and permissions
The issue proposes WordPress Application Password authentication. The credential must have access to the content selected for ingestion. WordPress notes that public REST resources may be available differently from private, password-protected, internal-user, custom-post-type, or metadata resources; those restricted resources generally require authorization or explicit exposure. Review the WordPress REST API handbook and verify the behavior of your own site and hosting configuration. The sources reviewed do not establish compatibility for every managed-hosting setup.
Incremental updates and deletions
The proposed modified_after filter is intended to retrieve content changed since an earlier sync rather than repeatedly reprocessing everything. The issue also asks that content deleted from WordPress be removed from Cognee’s graph on the next sync. These are requirements in the open proposal, not verified features of a released connector.
Do not confuse this with WordPress 7.0’s Connectors API
WordPress 7.0 introduces a Connectors API and a Settings → Connectors screen for registering connections to external services, initially focused on external-service connections and AI providers. That framework is distinct from the Cognee proposal: the latter is intended to read content out of WordPress and send it into Cognee. WordPress’s Connectors API announcement describes the framework; the Settings Connectors screen documentation explains credential handling. API keys entered in that screen are masked in the interface but are not encrypted when stored in the database; environment variables or PHP constants are alternatives for supplying credentials.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose a Cognee runtime after confirming the connector exists
Cognee documents both Cognee Cloud, a managed option, and a local Docker setup. These represent different operating responsibilities, not a tested ranking: with a managed service, deployment is handled through Cognee Cloud and API-key configuration; with local Docker, the operator runs and maintains the service. The Cognee API reference documents the available options, but does not compare their performance or suitability for a particular WordPress site.
Because the WordPress connector remains a proposal in the reviewed issue, first verify whether implementation has since been merged or released. Until then, treat content selection, Application Password access, incremental sync, deletion propagation, and setup instructions as requested behavior—not a feature you can assume is available.
Recommended Free Tools
Quick Recap
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.
