Maton SaaS MCP Server

### 1. Basic Configuration This is the minimal configuration to register the **Maton SaaS MCP Server** with Claude Code, using a simple command invocation and no extra options. ```json { "maton-saas": { "command": "maton-saas-mcp", "args": [], "env": {}, "disabled": false } } ``` **Explanation (not part of JSON):** - `"maton-saas"`: The ID Claude will use for this MCP server. You’ll refer to it by this name in Claude Code. - `"command"`: The executable for the Maton SaaS MCP Server. Adjust if it’s installed under a different name (e.g., `node maton-saas-mcp.js` or `docker`). - `"args"`: Empty array means no additional CLI arguments are passed. - `"env"`: Empty object – no environment variables are configured yet. - `"disabled": false`: Ensures the server is enabled and available in Claude Code. --- ### 2. Advanced Configuration A more complete configuration with environment variables, arguments, and a custom path. This might reflect a local Node-based server or a binary in a custom directory. ```json { "maton-saas": { "command": "/usr/local/bin/maton-saas-mcp", "args": [ "--log-level", "info", "--max-connections", "10", "--timeout-ms", "15000" ], "env": { "MATON_SAAS_API_KEY": "your-api-key-here", "MATON_SAAS_BASE_URL": "https://api.maton-saas.example.com", "MATON_SAAS_ENV": "development", "HTTP_PROXY": "", "HTTPS_PROXY": "" }, "disabled": false, "autoRestart": true, "timeoutSeconds": 60 } } ``` **Explanation (not part of JSON):** - `"command"`: Absolute path to the Maton SaaS MCP Server binary/script. - `"args"`: - `"--log-level", "info"`: Enables informational logs from the server. - `"--max-connections", "10"`: Example performance tuning option (if supported). - `"--timeout-ms", "15000"`: Example request timeout in milliseconds. - `"env"`: - `"MATON_SAAS_API_KEY"`: API key or token for authenticating with the Maton SaaS backend. - `"MATON_SAAS_BASE_URL"`: Base URL of your Maton SaaS deployment or region endpoint. - `"MATON_SAAS_ENV"`: Environment label (e.g., `development`, `staging`, `production`). - `"HTTP_PROXY"` / `"HTTPS_PROXY"`: Set if you need a proxy; left empty here. - `"autoRestart": true`: Lets Claude restart the MCP server if it crashes. - `"timeoutSeconds": 60`: Maximum time Claude waits for the server to respond to a request. --- ### 3. Use Case Specific Configuration – Production SaaS Workspace Orchestration This configuration is tailored for a **production** setup where Maton SaaS is used to orchestrate and manage multiple SaaS tools (e.g., CRM, ticketing, docs) from Claude. It assumes stricter timeouts, read-only mode for safety, and a dedicated workspace. ```json { "maton-saas": { "command": "docker", "args": [ "run", "--rm", "-i", "--network", "maton-saas-net", "-e", "MATON_SAAS_API_KEY", "-e", "MATON_SAAS_BASE_URL", "-e", "MATON_SAAS_ENV", "-e", "MATON_SAAS_WORKSPACE_ID", "-e", "MATON_SAAS_READ_ONLY", "maton-saas/mcp-server:latest" ], "env": { "MATON_SAAS_API_KEY": "prod-xxxxxxxxxxxxxxxx", "MATON_SAAS_BASE_URL": "https://api.maton-saas.yourcompany.com", "MATON_SAAS_ENV": "production", "MATON_SAAS_WORKSPACE_ID": "workspace-ops-001", "MATON_SAAS_READ_ONLY": "true" }, "disabled": false, "autoRestart": true, "timeoutSeconds": 30 } } ``` **Explanation (not part of JSON):** - This assumes the Maton SaaS MCP Server is packaged as a Docker image: `maton-saas/mcp-server:latest`. - `"command": "docker"` with `"args"`: - `"run", "--rm", "-i"`: Run an ephemeral interactive container. - `"--network", "maton-saas-net"`: Attach to a custom Docker network where internal SaaS services or proxies may live. - `-e ...`: Pass environment variables from the host into the container. - `"env"`: - `"MATON_SAAS_API_KEY"`: Production API key with restricted, audited permissions. - `"MATON_SAAS_BASE_URL"`: Production Maton SaaS endpoint for your company. - `"MATON_SAAS_ENV": "production"`: Ensures server uses production configs (logging, rate limits, etc.). - `"MATON_SAAS_WORKSPACE_ID"`: Locks this MCP to a specific org/workspace (e.g., Ops or Support). - `"MATON_SAAS_READ_ONLY": "true"`: Safety setting to allow Claude to query SaaS systems (tickets, CRM records, dashboards) but not modify them in production. - `"timeoutSeconds": 30`: Stricter timeout appropriate for production responsiveness. - `"autoRestart": true`: Keeps the integration resilient to transient failures.