Billing Schedule — affectUI MCP Resource
Billing Schedule
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 Billing Schedule from your client
- Claude Code affectUI Resource/Billing Schedule run in your project directory
- Claude Desktop affectUI Resource/Billing Schedule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor affectUI Resource/Billing Schedule ~/.cursor/mcp.json
- VS Code affectUI Resource/Billing Schedule .vscode/mcp.json
- Zed affectUI Resource/Billing Schedule ~/.config/zed/settings.json
- Windsurf affectUI Resource/Billing Schedule ~/.codeium/windsurf/mcp_config.json
- Cline affectUI Resource/Billing Schedule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI affectUI Resource/Billing Schedule ~/.gemini/settings.json
- Grok affectUI Resource/Billing Schedule .mcp.json (in your project root)
- ChatGPT affectUI Resource/Billing Schedule Settings → Connectors → Advanced → Developer mode
- Claude.ai affectUI Resource/Billing Schedule Settings → Connectors → Add custom connector
- LangChain affectUI Resource/Billing Schedule 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
- 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
- Email Draft
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.