BotCreds Agent Memory
| 开发者 |
jboydston
botcreds |
|---|---|
| 更新时间 | 2026年6月23日 02:51 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
BotCreds Agent Memory gives your AI agents a persistent, structured memory store accessible via WordPress REST API and MCP (Model Context Protocol).
Two modes of operation:
- KV Mode (default) — Simple key-value store with tags, expiry, and text search. No external dependencies. Works out of the box.
- Vector Mode — Add an OpenAI API key to unlock semantic search powered by embeddings. Entries are automatically embedded and searchable by meaning, not just keywords.
- REST API with full CRUD (create, read, update, delete)
- MCP endpoint for AI agent tool integration
- Namespace-based access control per WordPress user
- Automatic embedding generation via WP-Cron
- Bulk backfill for existing entries
- Expiry support for temporary memories
- Tag-based filtering and organization
- WordPress Application Password authentication
安装:
- Upload the
botcreds-agent-memoryfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- (Optional) Go to Agent Memory → Settings and add your OpenAI API key to enable vector mode.
- Create a WordPress Application Password for your agent under Users → Profile → Application Passwords.
- Use the REST API at
/wp-json/botcreds-memory/v1/with Basic Auth.
常见问题:
Do I need an OpenAI API key?
No. Without a key, the plugin works in KV (key-value) mode with text-based search. An OpenAI key enables semantic vector search via embeddings.
How does authentication work?
The plugin uses WordPress Application Passwords. Create one under Users → Profile → Application Passwords, then use HTTP Basic Auth with your username and the generated password.
Can I restrict which keys a user can access?
Yes. Go to Users → Edit User → Agent Memory Access and set allowed key prefixes. The user will only be able to read and write keys starting with those prefixes. Leave blank for full access.
What is MCP?
MCP (Model Context Protocol) is a standard for AI agents to discover and use tools. The plugin exposes an MCP manifest at /wp-json/botcreds-memory/v1/mcp and a tool call endpoint at /wp-json/botcreds-memory/v1/mcp/call.
How are embeddings generated?
When you save an entry and an OpenAI key is configured, the plugin schedules a WP-Cron event to generate the embedding asynchronously. Existing entries can be backfilled from the Settings page.
What embedding model is used?
By default, text-embedding-3-small (1536 dimensions). You can change this in the Settings page.
更新日志:
2.3.3
- Changed: agent_type now auto-populated from BotCreds credential label; no longer requires X-Agent-Type header or MCP param
- Added: agent_type field on revisions — capture which agent made each write (e.g. "Claude Desktop", "OpenClaw")
- Added: X-Agent-Type request header support on REST writes
- Added: agent_type parameter on set_memory MCP tool
- Fixed: revisions table not created on update from v2.2.x (version check race condition)
- Fixed: missing revisions_table_name() method caused silent revision write failures
- Added: Revision history — every write creates a revision with author attribution
- Added:
GET /entries/revisions?key=REST endpoint — full audit trail per entry - Added: MCP tool
get_revisions(key)— ask who changed what and when - Added: Author capture on all writes (WP user id + display name)
- Added: Namespaces — keys support
/-delimited paths (e.g.project/clawpress/brief), auto-indexed - Added:
GET /namespacesREST endpoint — browse namespace tree with entry counts - Added:
GET /tagsREST endpoint — list all tags with counts - Added:
?namespace=and?tag=filter params onGET /entries - Added: MCP tools
get_by_tag,list_namespaces,list_tags - Added:
namespaceandtagparams onlist_memoryandsearch_memoryMCP tools - Improved: tag filtering now supports
?tag=query param (single tag) alongside existing?tags=(CSV)
- Change: Site hardening is now disabled by default. It was previously enabled by default, which could block front-end traffic on existing sites.
- Add: Hardening toggle added to Agent Memory > Settings > Site Hardening with clear warning label.
- Add:
botcreds_memory_hardenedoption registered via Settings API (sanitized, integer, default 0).
- Fix: Remove invalid
botcredscontributor (not a WordPress.org username). - Fix: Add Plugin URI and License URI to plugin header to match BotCreds branding standards.
- Fix: Align tags to hyphenated format and lower Requires at least to 5.6.
- Fix: Replace non-standard bcam prefix with botcreds_memory in admin page slug, hook names, nonce actions, and POST key names for WordPress.org review compliance.
- Fix fatal error on settings pages: guard Settings API registration with is_admin() check.
- Fix PHP 7.4 compatibility: replace str_starts_with() with strpos()-based equivalent.
- Register plugin settings on rest_api_init so show_in_rest works correctly.
- Expose OpenAI key and embedding model settings via the REST API.
- Security hardening: return 403 for unauthenticated HTML requests to the frontend.
- MCP: implement proper JSON-RPC 2.0 protocol for tool calls and responses.
- Update plugin author to Joe Boydston.
- Add jboydston as WordPress.org contributor.
- Fix Plugin Check errors: SQL preparation phpcs:ignore annotations, nonce verification in user profile save, i18n ordered placeholders, error_log wrapped in WP_DEBUG guard.
- Update tested up to WordPress 7.0.
- Initial public release.
- KV mode: key-value store with tags, expiry, and text search.
- Vector mode: semantic search via OpenAI embeddings.
- REST API: full CRUD under
/wp-json/botcreds-memory/v1/. - MCP endpoint: manifest and tool call handler.
- Access control: per-user namespace restrictions.
- Admin UI: entries browser, settings page, access control overview.
- WP-Cron: automatic embedding generation and bulk backfill.