🧭 Type of Feature
🧭 Epic
Title: CPEX Plugin Framework MCP SDK Compatibility Investigation
Goal: Determine if the current CPEX plugin framework is compatible with the MCP SDK version 2026-07-28 and identify any breaking changes or required updates.
Why now: The MCP SDK 2026-07-28 may introduce changes that affect plugin framework integration. We need to assess compatibility before upgrading or making architectural decisions.
🧑🏻💻 Investigation Scope
As a: Platform developer
I want: To understand CPEX compatibility with MCP SDK 2026-07-28
So that: We can plan necessary updates and avoid breaking changes in production
✅ Investigation Deliverables
📐 Investigation Areas
Key areas to examine:
-
Hook Interface Changes
- Verify
prompt_pre_fetch, prompt_post_fetch, tool_pre_invoke, tool_post_invoke, resource_pre_fetch, resource_post_fetch signatures
- Check payload and result types
-
External Plugin Protocol
- STREAMABLEHTTP and STDIO transport compatibility
- Required tool signatures (
get_plugin_config, hook tools)
-
Plugin Configuration Schema
- Verify
plugins/config.yaml structure compatibility
- Check
kind, hooks, mode, priority fields
-
Framework Dependencies
- Review
cpex package version requirements
- Check for deprecated imports or APIs
🔗 MCP Standards Check
📓 Additional Context
- Current CPEX framework:
cpex package (ContextForge Plugin Extensions)
- Plugin directory:
plugins/ with 42+ plugin implementations
- Configuration:
plugins/config.yaml (Jinja-enabled)
- Related docs:
plugins/AGENTS.md, plugins/README.md
Success Criteria:
- Clear compatibility assessment documented
- List of required changes (if any) with effort estimates
- Recommendation for next steps (upgrade path or maintain current version)
🧭 Type of Feature
🧭 Epic
Title: CPEX Plugin Framework MCP SDK Compatibility Investigation
Goal: Determine if the current CPEX plugin framework is compatible with the MCP SDK version 2026-07-28 and identify any breaking changes or required updates.
Why now: The MCP SDK 2026-07-28 may introduce changes that affect plugin framework integration. We need to assess compatibility before upgrading or making architectural decisions.
🧑🏻💻 Investigation Scope
As a: Platform developer
I want: To understand CPEX compatibility with MCP SDK 2026-07-28
So that: We can plan necessary updates and avoid breaking changes in production
✅ Investigation Deliverables
📐 Investigation Areas
Key areas to examine:
Hook Interface Changes
prompt_pre_fetch,prompt_post_fetch,tool_pre_invoke,tool_post_invoke,resource_pre_fetch,resource_post_fetchsignaturesExternal Plugin Protocol
get_plugin_config, hook tools)Plugin Configuration Schema
plugins/config.yamlstructure compatibilitykind,hooks,mode,priorityfieldsFramework Dependencies
cpexpackage version requirements🔗 MCP Standards Check
📓 Additional Context
cpexpackage (ContextForge Plugin Extensions)plugins/with 42+ plugin implementationsplugins/config.yaml(Jinja-enabled)plugins/AGENTS.md,plugins/README.mdSuccess Criteria: