Cursor

  • Connects: to either. The hosted server goes in mcp.json with the URL. logMcp runs over stdio when log is on the same machine.
  • Draws MCP Apps: yes, since Cursor 2.6. Apps run in a sandboxed iframe. (Cursor 2.6: MCP Apps)
    • Cursor is listed in the support matrix.
    • One user reported apps stopped rendering in a later version. (forum report) That's a single report, not confirmed, so test on the current version.
  • Guidance:
    • Prompt hooks: Cursor has them, but beforeSubmitPrompt can only let a prompt through or block it; it can't add context. Only sessionStart and the tool hooks can (additional_context). (Cursor hooks)
    • Prompt router: so the model routes each request with getGuide({ ask: "<the owner's words>" }), as getGuide's description says.
    • log's hooks: the repo's .cursor/hooks.json, written from AGENT_HOOKS by bun run check:agentHooks --write, runs scripts/hooks/event.ts on sessionStart and postToolUse with --host cursor, which answers { "additional_context": … } cut to 7,500 characters: browser states, storage, engines, the knowledge base, pending inbox messages and the X queue. Nothing installs it for a user outside the checkout yet.
    • Server instructions: whether Cursor passes them to the model isn't documented. The tool descriptions name getGuide either way.
  • Not verified:
    • log's view and sign-in in Cursor
    • which widget actions Cursor supports
    • whether a beforeSubmitPrompt hook can add context for the model, the way Claude Code's UserPromptSubmit can

On this page

No Headings