src/
  index.ts             MCP server entry point (stdio transport)
  server-config.ts     Environment-based connection configuration
  tools/
    users.ts           8 tools  — user CRUD, disable/enable, password reset
    roles.ts           7 tools  — role listing, permission checks, assign/revoke
    jobs.ts            7 tools  — job status, running/failed lists, cancel, retry
    scheduler.ts       7 tools  — schedule management, upcoming jobs, history
    batch.ts           6 tools  — batch status, rerun, cancel, history
    audit.ts           6 tools  — log search, user activity, export, login history
    config.ts          7 tools  — config validation, health check, compare envs

# Clone or download the project
cd c:\NewInitiatives\mcp\mcp-isuite

# Install dependencies (zero vulnerabilities)
npm install

copy .env.example .env

# Required
ISUITE_BASE_URL=https://isuite.yourcompany.com/api/v1
ISUITE_API_KEY=your-api-key-here

# Auth type: apikey | bearer | basic
ISUITE_AUTH_TYPE=apikey

# For basic auth only
ISUITE_USERNAME=
ISUITE_PASSWORD=

# Optional
ISUITE_ENVIRONMENT=production
ISUITE_TIMEOUT_MS=30000
ISUITE_VERIFY_TLS=true

npm run build

node dist/index.js
# Expected output on stderr: iSuite Operations MCP server running on stdio

{
  "mcpServers": {
    "isuite": {
      "command": "node",
      "args": ["c:/NewInitiatives/mcp/mcp-isuite/dist/index.js"],
      "env": {
        "ISUITE_BASE_URL": "https://isuite.yourcompany.com/api/v1",
        "ISUITE_API_KEY": "your-api-key-here",
        "ISUITE_AUTH_TYPE": "apikey",
        "ISUITE_ENVIRONMENT": "production",
        "ISUITE_TIMEOUT_MS": "30000"
      },
      "disabled": false,
      "alwaysAllow": []
    }
  }
}

Ctrl+Shift+P → Roo Code: Open MCP Settings

{
  "mcpServers": {
    "isuite": {
      "command": "node",
      "args": ["c:/NewInitiatives/mcp/mcp-isuite/dist/index.js"],
      "env": {
        "ISUITE_BASE_URL": "https://isuite.yourcompany.com/api/v1",
        "ISUITE_API_KEY": "your-api-key-here",
        "ISUITE_AUTH_TYPE": "apikey",
        "ISUITE_ENVIRONMENT": "production",
        "ISUITE_TIMEOUT_MS": "30000"
      },
      "disabled": false,
      "alwaysAllow": [
        "list_users",
        "get_user",
        "list_roles",
        "get_user_roles",
        "list_running_jobs",
        "list_failed_jobs",
        "get_job_status",
        "list_schedules",
        "get_scheduler_status",
        "list_running_batches",
        "search_audit_logs",
        "check_system_health",
        "get_config_value",
        "list_config_keys"
      ]
    }
  }
}

{
  "mcpServers": {
    "isuite": {
      "command": "node",
      "args": ["c:/NewInitiatives/mcp/mcp-isuite/dist/index.js"],
      "env": {
        "ISUITE_BASE_URL": "https://isuite.yourcompany.com/api/v1",
        "ISUITE_API_KEY": "your-api-key-here",
        "ISUITE_ENVIRONMENT": "staging"
      }
    }
  }
}

{
  "mcpServers": {
    "isuite": {
      "command": "node",
      "args": ["c:/NewInitiatives/mcp/mcp-isuite/dist/index.js"],
      "env": {
        "ISUITE_BASE_URL": "https://isuite.yourcompany.com/api/v1",
        "ISUITE_API_KEY": "your-api-key-here",
        "ISUITE_AUTH_TYPE": "apikey",
        "ISUITE_ENVIRONMENT": "production"
      }
    }
  }
}

List all active iSuite users in the Finance department and show me
which roles each one has assigned.

Create a new iSuite user account for Jane Smith (jsmith@company.com)
in the Operations department. Assign her the OPERATOR and BATCH_RUNNER
roles, and send a welcome email.

User john.doe hasn't logged in for 90 days. Check his account status,
list his current roles, then disable the account with the reason
"Inactive account — 90 day policy".

I need to audit who has the ADMIN role in iSuite. List all members
of that role and verify whether any of them also have the SCHEDULER_ADMIN
role at the same time.

Show me all currently running iSuite jobs. For any job that has been
running longer than 2 hours, get its full status and step details.

List all failed jobs from the last 24 hours. Group them by job type
and tell me which type has the highest failure rate.

Job execution JOB-20240612-0042 is stuck. Check its current status,
then cancel it gracefully with the reason "Manual intervention — stuck job".
After cancellation, retry it from the failed step.

Get the full execution history for job definition ETL-DAILY-SALES
for the past 30 runs. Summarize average duration, success rate,
and identify any patterns in failures.

Show me all scheduled jobs that are set to run in the next 6 hours.
Highlight any that overlap in timing and might cause resource contention.

The end-of-month batch window starts tomorrow. Disable all non-critical
schedules (type: report) for the next 24 hours to free up resources.
List which ones you disabled.

Get the scheduler engine status and list all currently disabled schedules.
Tell me which ones have been disabled longest.

Show me all batch jobs that are currently running. For each one,
show progress percentage and estimated completion time.

Batch job BATCH-RECON-2024-0610 failed overnight. Get its full status
including step details, then rerun it from the failed step with
normal priority.

Get the last 20 executions of the MONTH-END-CLOSE batch. Summarize
average runtime, any failures, and whether performance has degraded
over the last 5 runs compared to the previous 15.

Search the audit logs for all CONFIG_UPDATE actions performed in the
last 7 days. Show me who made changes, what was changed, and when.

Pull all activity for user admin.user from the past 30 days.
Summarize the types of actions they performed and flag anything
that looks unusual (e.g. bulk deletes, after-hours logins, role changes).

Export the full audit trail for June 2024 to CSV format.
Include only events related to job cancellations and batch reruns.

Show me all failed login attempts in the last 48 hours.
Group by username and highlight any accounts with more than
3 failed attempts — these may need to be locked.

Run a full iSuite system health check across all subsystems.
Summarize which are healthy, which have warnings, and which are failing.

Validate the entire iSuite configuration in strict mode.
List all errors and warnings and suggest remediation steps.

Compare the iSuite configuration between production and staging environments.
Highlight every difference and flag any production settings that look
risky if accidentally used in staging.

Check the database connection health and validate the SMTP connection.
If either fails, show the full error details from the config.

What is the current value of scheduler.maxConcurrentJobs?
Also list all configuration keys under the scheduler section
so I can review the full scheduler configuration.

Do a daily operations check:
1. Show all currently running jobs and batches
2. List any failed jobs or batches from the last 12 hours
3. Show upcoming scheduled jobs in the next 4 hours
4. Run a system health check
Give me a summary with any action items.

User sarah.jones is leaving the company today. 
1. Get her current profile and role assignments
2. Revoke all her roles with reason "Employee offboarding"
3. Disable her account
4. Show her audit activity from the last 30 days for compliance records

Before the production deployment tonight:
1. Validate the full iSuite configuration
2. Check system health
3. List any jobs currently running that might be affected
4. Show upcoming scheduled jobs in the next 8 hours that could conflict
Summarize the go/no-go status.

npm run build