Skip to content

fix(cursor): isolate runtime MCP plugins - #621

Draft
TiantianFlow wants to merge 1 commit into
awslabs:mainfrom
TiantianFlow:fix/cursor-mcp-config
Draft

fix(cursor): isolate runtime MCP plugins#621
TiantianFlow wants to merge 1 commit into
awslabs:mainfrom
TiantianFlow:fix/cursor-mcp-config

Conversation

@TiantianFlow

@TiantianFlow TiantianFlow commented Aug 15, 2026

Copy link
Copy Markdown
Contributor

Summary

  • materialize CAO’s bundled cao-mcp-server as a schema-conformant, terminal-private Agent Plugin under CAO temporary storage
  • pass the plugin through --plugin-dir with --approve-mcps; no project .cursor/mcp.json is created or changed
  • reject unsupported/nonportable MCP profile configuration before launch instead of emitting a plugin Cursor would ignore
  • make command construction use one profile snapshot and add concurrent same-CWD isolation coverage

Validation

  • UV_PROJECT_ENVIRONMENT=/private/tmp/cursor-mcp-pr-validation-venv uv run pytest test/providers/test_cursor_cli_unit.py (93 passed)
  • black --check, isort --check-only, and git diff --check

Scope

This stays draft pending independent re-review. It adds the CAO runtime MCP bridge only; other MCP servers should use a Cursor-native plugin. It does not resolve Cursor account/keychain authentication.

@TiantianFlow TiantianFlow changed the title fix(cursor): materialize project MCP config fix(cursor): isolate runtime MCP plugins Aug 15, 2026
@TiantianFlow
TiantianFlow force-pushed the fix/cursor-mcp-config branch from 809a2c8 to 0038bfc Compare August 15, 2026 02:32
@TiantianFlow
TiantianFlow force-pushed the fix/cursor-mcp-config branch from 0038bfc to cca6f03 Compare August 15, 2026 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant