outseta-admin

This MCP server enables AI assistants to manage your Outseta account through natural language commands. It exposes tools for Account & People management, Billing Plans, Subscriptions, and Email Lists, allowing you to create, update, list, and query data within Outseta without switching UI. To use it, configure the MCP client (for example Cursor or Claude Desktop) to connect to the server using the prescribed npx command and provide your Outseta credentials (subdomain, API key, and secret). Once connected, the AI assistant will route relevant intents to the Outseta admin MCP server, handle parameter validation, and prompt for confirmation before destructive actions. You can connect multiple MCP server configurations to manage more than one Outseta account or environment, enabling seamless cross-account operations from a single assistant.

Prerequisites:\n- Node.js (version 18 or higher) and npm/yarn installed on your machine.\n- An active Outseta account with admin access.\n- Outseta API credentials (subdomain, API key, API secret).\n- MCP-compatible AI assistant (e.g., Cursor, Claude Desktop).

Installation steps:\n1) Install the MCP server package via npx (no local install required):\n - Ensure you have an API key/secret and subdomain from your Outseta account.\n - When configuring your MCP client, use:\n npx -y @outseta/admin-mcp-server\n\n2) Alternatively, install locally (optional):\n - npm install -g @outseta/admin-mcp-server\n - Run with the required environment variables.\n\n3) Configure your MCP client with the required environment variables:\n - OUTSETA_SUBDOMAIN=your-subdomain\n - OUTSETA_API_KEY=your-api-key\n - OUTSETA_API_SECRET=your-api-secret\n\n4) Start using the MCP server through your preferred AI assistant by adding the server configuration: the typical example uses:\n name: outseta-admin\n command: npx\n args: [-y, @outseta/admin-mcp-server]\n env: { OUTSETA_SUBDOMAIN, OUTSETA_API_KEY, OUTSETA_API_SECRET }

Tips and notes:\n- Keep API credentials secure; rotate keys regularly and use separate keys per account/env when using multiple MCP configurations.\n- If the assistant asks for confirmation before destructive changes (e.g., deleting a person or downgrading a plan), review and approve to proceed.\n- For multiple accounts, configure distinct MCP server entries (different names) with the appropriate OUTSETA_SUBDOMAIN and keys.\n- Ensure your Outseta account has the required permissions for the actions you want to perform via the MCP server.\n- If you encounter connectivity issues, verify network access to Outseta endpoints and that the subdomain, API key, and secret are correctly set in the environment.\n- When using with Cursor or Claude Desktop, restart the app after adding or updating MCP server configurations to ensure the new server is loaded.