Store header and footer — Nasaq UI MCP Resource
Store header and footer
is one of 391 resources on the
Nasaq UI
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Store header and footer from your client
- Claude Code Nasaq UI Resource/Store header and footer run in your project directory
- Claude Desktop Nasaq UI Resource/Store header and footer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Nasaq UI Resource/Store header and footer ~/.cursor/mcp.json
- VS Code Nasaq UI Resource/Store header and footer .vscode/mcp.json
- Zed Nasaq UI Resource/Store header and footer ~/.config/zed/settings.json
- Windsurf Nasaq UI Resource/Store header and footer ~/.codeium/windsurf/mcp_config.json
- Cline Nasaq UI Resource/Store header and footer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Nasaq UI Resource/Store header and footer ~/.gemini/settings.json
- Grok Nasaq UI Resource/Store header and footer .mcp.json (in your project root)
- ChatGPT Nasaq UI Resource/Store header and footer Settings → Connectors → Advanced → Developer mode
- Claude.ai Nasaq UI Resource/Store header and footer Settings → Connectors → Add custom connector
- LangChain Nasaq UI Resource/Store header and footer pip install langchain-mcp-adapters
Other resources on this server
- catalog
- AccessGrants
- Accordion
- AccountSettings
- Accounting Ledger
- ActiveSessions
- Activity Composer
- AddressInput
- AdminArea
- AdminWorkspaces
- AdminUsers
- AgentPersonaEditor
- Agent Steps and Confirm
- AI Citations and Provenance
- AiModelPicker
- AI States
- AiUsageCost
- Alert
- AlertDialog
- AlertList
- AnalyticsConnect
- ApiKeys
- API reference
- ApmPage
- APM panels
- AppShell
- AppUpdate
- Appearance pickers
- ApprovalQueue
- Artifact Renderer
- Ask AI and Insight Card
- AspectRatio
- Attention
- AuditLog
- AuthLayout
- AvailabilityEditor
- Avatar
- AvatarUpload
- BacklinkMonitor
- BackupManager
Read from the server itself, by connecting to it and calling resources/list on 11 October 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.