Permission Request — affectUI MCP Resource
Permission Request
is one of 142 resources on the
affectUI
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Permission Request from your client
- Claude Code affectUI Resource/Permission Request run in your project directory
- Claude Desktop affectUI Resource/Permission Request ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor affectUI Resource/Permission Request ~/.cursor/mcp.json
- VS Code affectUI Resource/Permission Request .vscode/mcp.json
- Zed affectUI Resource/Permission Request ~/.config/zed/settings.json
- Windsurf affectUI Resource/Permission Request ~/.codeium/windsurf/mcp_config.json
- Cline affectUI Resource/Permission Request ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI affectUI Resource/Permission Request ~/.gemini/settings.json
- Grok affectUI Resource/Permission Request .mcp.json (in your project root)
- ChatGPT affectUI Resource/Permission Request Settings → Connectors → Advanced → Developer mode
- Claude.ai affectUI Resource/Permission Request Settings → Connectors → Add custom connector
- LangChain affectUI Resource/Permission Request pip install langchain-mcp-adapters
Other resources on this server
- index
- Agent Checkpoints
- Agent Cursors
- Agent Findings
- Agent Fleet
- Agent Graph
- Agent Handoff
- Agent Inbox
- Agent Lanes
- Agent Ledger
- Agent Monitor
- Agent Plan
- Agent Queue
- Agent Recap
- Agent Steering
- Agent Tree
- AI Answer
- Approval Card
- Autonomy Dial
- Billing Schedule
- Breakdown Chart
- Button
- Change Summary
- Chat Composer
- Cited Answer
- Combobox
- Command Menu
- Comment Thread
- Comments Panel
- Compact Breakdown
- Conflict Radar
- Context Map
- Context Window
- Cost Waterfall
- Data Table
- Date Range Picker
- Decision Inbox
- Decision Tree
- Delegate Board
- Dropzone
affectUI also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.