PayGate Server Directory — PayGate MCP — Monetization Gateway for AI Agents MCP Resource

PayGate Server Directory is one of 1 resource on the PayGate MCP — Monetization Gateway for AI Agents MCP server. Connect the server and your client can attach it as context.

by client

How to attach PayGate Server Directory from your client

• Claude Code PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory run in your project directory
• Claude Desktop PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/.cursor/mcp.json
• VS Code PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory .vscode/mcp.json
• Zed PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/.config/zed/settings.json
• Windsurf PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/.codeium/windsurf/mcp_config.json
• Cline PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory ~/.gemini/settings.json
• Grok PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory .mcp.json (in your project root)
• ChatGPT PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory Settings → Connectors → Advanced → Developer mode
• Claude.ai PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory Settings → Connectors → Add custom connector
• LangChain PayGate MCP — Monetization Gateway for AI Agents Resource/PayGate Server Directory pip install langchain-mcp-adapters

PayGate MCP — Monetization Gateway for AI Agents also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 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.