Abilities Bridge
| 开发者 | joe12345campbell |
|---|---|
| 更新时间 | 2026年6月4日 13:53 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Making Connections Possible | Now with Claude Opus 4.8, in-chat image attachments and screenshots, GPT-5.5, and Custom Apps in ChatGPT
Abilities Bridge connects AI to your WordPress site. Use the built-in admin chat, connect via MCP to Claude Desktop, or integrate with other MCP-compatible applications. Supports both Anthropic (Claude) and OpenAI models.
Key Features
- Admin chat interface for direct AI interaction
- Image attachments in chat — upload images or capture a browser-approved screenshot (can be disabled in settings)
- MCP server for Claude Desktop, ChatGPT, and other MCP clients
- Persistent memory storage across conversations
- Abilities execution with 7-gate permission controls
- Integrated Connected Plugins — discover and approve AI abilities that other plugins register, with per-ability permission controls
- Claude and OpenAI model support
- OAuth 2.0 authentication for MCP connections
- Admin Chat - Built-in interface using your Anthropic or OpenAI API key
- Claude Custom Connector - Connect Claude Desktop using your Claude subscription (no API key needed)
- ChatGPT Developer Mode - Connect ChatGPT using the built-in MCP endpoint with OAuth
- Local MCP Config - Connect Claude Code and other apps using API key or Claude account
- WordPress 6.2+, PHP 7.4+
- Anthropic API key, OpenAI API key, or Claude account (depending on connection method)
- HTTPS required for MCP OAuth 2.0 connections
安装:
- Upload the
abilities-bridgefolder to/wp-content/plugins/ - Activate the plugin through the 'Plugins' menu
- Complete the welcome wizard to grant consent
- Enter your Anthropic or OpenAI API key in Settings, or set up MCP in Settings > MCP Setup
- Go to Abilities Bridge > Settings > Anthropic MCP
- Click "Generate New Anthropic Client Credentials"
- Save both Client ID and Client Secret
- In Claude Desktop: Settings > Connectors > Add custom connector
- Enter credentials and MCP endpoint URL from WordPress
- Go to Abilities Bridge > Settings > OpenAI ChatGPT MCP
- Click "Generate New ChatGPT Client Credentials"
- Save both Client ID and Client Secret
- In ChatGPT: Settings > Apps > Advanced Settings > Enable developer mode
- Create app, add MCP endpoint URL, choose OAuth, and enter credentials
屏幕截图:
常见问题:
Do I need an API key?
For the admin chat interface, yes - an Anthropic or OpenAI API key is required. For MCP via Claude Desktop, you only need a Claude account (no API key needed). For ChatGPT, you need a ChatGPT account with developer mode enabled.
Where do I get an API key?
- Anthropic: https://console.anthropic.com/
- OpenAI: https://platform.openai.com/
Do I need the Abilities API?
Yes. The Abilities API is the official WordPress API for AI. It comes standard with WordPress 6.9 and is also available as a plugin.
Is this safe to use?
All capabilities require explicit consent. Abilities use a 7-gate permission system with rate limits, risk levels, and admin approval. All actions are logged.
What data is sent to external services?
Chat messages, memory contents, and abilities execution requests are sent to your selected AI provider. Data is only sent when you actively use the plugin. No telemetry or usage statistics are collected.
What is the Memory Tool?
An optional feature that lets AI store persistent notes in the WordPress database across conversations. Limited to 1MB per entry, 50MB total. Enable in Settings > Memory.
What are Abilities?
AI-callable WordPress functions (creating posts, managing users, etc.) that must be individually authorized. Each ability is controlled by rate limits, risk levels, and approval requirements.
What is Beacon Campaign Sender?
Beacon Campaign Sender is a separate plugin that connects to Abilities Bridge as an Integrated Connected Plugin. When it is installed and active, it registers its tools with Abilities Bridge and they appear on the Integrations page. Approve them with one click to let AI agents use Beacon's tools, with the same per-ability permission controls as every other ability. Nothing is enabled until you approve it.
更新日志:
1.3.2
- MCP discovery (initialize, tools/list, ping) now requires authentication for every client, the same as running a tool; the unauthenticated pre-OAuth discovery added in 1.3.1 has been removed. This fixes Claude custom connectors (which connect authenticate-first); ChatGPT connects the same way via OAuth
- Unauthenticated MCP requests now return an HTTP 401 with a WWW-Authenticate challenge so MCP clients reliably start the OAuth flow
- MCP discovery (initialize, tools/list, ping) is now available before OAuth so remote app builders such as ChatGPT Apps can discover actions and then authenticate; running a tool still requires authentication
- Ability names are now mapped to MCP-safe tool names and resolved back by lookup, fixing tool calls for abilities whose names contain underscores
- Chat now returns a useful summary of tool results when the AI provider completes a tool action but returns no final text, instead of getting stuck on a "response pending" message
- Simplified the floating chat bubble by removing the in-bubble provider and model selectors
- Replaced browser confirm/alert popups in the admin chat with inline messages and a two-click delete confirmation
- Added chat image attachments — upload images or capture a browser-approved screenshot in the main chat and floating bubble (JPEG/PNG/WebP, up to 3 per message)
- Added an "Enable image attachments" setting to turn the upload and screenshot feature on or off
- Added Claude Opus 4.8 support and relabeled Opus 4.7
- Context-usage warning now scales to the model's context window instead of firing at fixed token counts
- Private attachment storage with server-side validation and authenticated, ownership-checked serving; files are cleaned up on conversation delete and plugin uninstall
- Replaced hardcoded Connected Plugins detection with the documented abilities_bridge_plugin_integrations contract
- Added validation, safe per-callback discovery, disabled integration cards, profile-aware approvals, and partial approval messages
- Added cleanup notice for old beacon-send/* approvals from pre-release Beacon Send integrations
- Breaking change for private/pre-release partner integrations: providers must register themselves through the integration filter
- Added Claude Opus 4.7 model support (most intelligent option)
- Added GPT-5.5 model support (now the default OpenAI option)
- Added Connected Plugins admin page for discovering and approving Abilities Bridge integrations
- Added per-model guidance text in the chat bubble and dashboard
- Conversation lookup, delete, and restore are now scoped to the current user — admins can no longer access other admins' conversations by ID
- OAuth consent now uses request-bound, single-use consent tokens with 5-minute transients
- Memory tool path validator no longer accepts paths sharing the /memories prefix but living outside the namespace (e.g. /memoriesXYZ)
- Default OpenAI model updated from GPT-5.4 to GPT-5.5
- Added WP AI Client credential integration for shared API keys via WordPress Connectors
- Added WP AI Client integration test page
- Added separate settings flows for Anthropic MCP and OpenAI ChatGPT MCP
- Added direct OpenAI ChatGPT MCP flow from built-in WordPress MCP endpoint
- Added floating chat bubble for administrators
- MCP OAuth client storage is now profile-aware
- MCP tools/list now filters visible tools using authenticated permissions
- OpenAI chat integration migrated to the Responses API
- Added GPT-5.4 model support
- Updated default OpenAI model to GPT-5.4
- Added OpenAI as an alternative AI provider
- Added Learn More tab with overview video and resources
- Updated Pro Features tab with Concierge Service and Site Abilities Plugin
- Initial release
- MCP server for WordPress Abilities execution
- Memory tool with database storage
- OAuth 2.0 authentication
- Admin chat interface