server_status

[debug]

Reports workspace readiness, load failures, cache state, and watcher activity.

Try it locally in the Glider playground

Parameters

Examples

Replace sample paths and symbol keys with values from your workspace.

Check if the server is running

{}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "server_status",
    "arguments": {}
  }
}

{
  "success": true,
  "serverRunning": true,
  "process": {
    "handles": 812,
    "privateMemoryMb": 2337,
    "threads": 50,
    "uptimeMinutes": 94,
    "sampledUtc": "2026-08-04T09:05:00Z",
    "diagnosticsLog": "~/.glidermcp/diagnostics"
  },
  "telemetryEnabled": false,
  "solutionLoaded": false,
  "solutionPath": null,
  "cache": {
    "cacheStatus": "empty",
    "revision": 0,
    "lastRefreshUtc": null,
    "loadedKind": "none",
    "loadedPath": null
  },
  "workspaceLoading": {
    "inProgress": true,
    "path": "/path/to/solution.sln",
    "kind": "solution",
    "startedUtc": "2026-01-12T21:06:03.123Z",
    "elapsedMs": 30000,
    "previousLoad": {
      "durationMs": 91000,
      "loadedUtc": "2026-01-11T09:14:02.000Z",
      "projectCount": 7
    },
    "estimatedRemainingMs": 61000,
    "advice": "Previous load of this workspace took ~91s; about 61s remaining. Re-check server_status in ~61s."
  },
  "workspaceWarmup": {
    "enabled": true,
    "inProgress": true,
    "path": "/path/to/solution.sln",
    "projectsWarmed": 42,
    "totalProjects": 117,
    "elapsedMs": 12000,
    "estimatedRemainingMs": 19000,
    "lastCompletedUtc": null,
    "lastDurationMs": null,
    "advice": "Compilation warm-up in progress (42/117 projects, ~19s remaining). Semantic tools work now, but first calls are slower until it completes."
  },
  "projectCount": 0,
  "lastLoadError": {
    "path": "/path/to/typo.sln",
    "kind": "solution",
    "trigger": "startup",
    "failedUtc": "2026-01-12T21:05:12.000Z",
    "durationMs": 12,
    "exceptionType": null,
    "message": "File not found: /path/to/typo.sln",
    "advice": "The --solution startup load failed; the server is running with no workspace. Fix the cause above, then call load."
  },
  "fileWatcher": {
    "enabled": false,
    "watchedDirectory": null,
    "pendingChanges": 0,
    "activeOperations": 0
  }
}

Inspect compact project format counts

{
  "includeProjectFormatSummary": true
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "server_status",
    "arguments": {
      "includeProjectFormatSummary": true
    }
  }
}

Inspect grouped workspace load diagnostics

{
  "includeWorkspaceDiagnostics": true
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "server_status",
    "arguments": {
      "includeWorkspaceDiagnostics": true
    }
  }
}

Inspect raw workspace load diagnostics

{
  "includeWorkspaceDiagnostics": true,
  "workspaceDiagnosticsView": "raw"
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "server_status",
    "arguments": {
      "includeWorkspaceDiagnostics": true,
      "workspaceDiagnosticsView": "raw"
    }
  }
}

Response Notes

Optionally includes cached workspace load diagnostics and compact project format counts.

Returns server/workspace status, cache metadata, watcher stats, an in-progress load summary under workspaceLoading (with an ETA when a previous load time is known), the background analysis warm-up state under workspaceWarmup (progress, ETA, and advice while the post-load warm-up runs; semantic tools work during it but first calls are slower), the most recent failed load under lastLoadError (path, kind, whether it came from the load tool or the startup preload, the exception type, and the failure text including MSBuild diagnostics - null once a load succeeds, so an empty workspace can be told apart from a failed one), and whether anonymous telemetry is enabled. Workspace load diagnostics and project format counts are included only when requested.

Glider 13.2.0 and later add a sanitized <code>license</code> block. It includes <code>environment</code>, <code>state</code>, <code>valid</code>, <code>commercialRights</code>, <code>paidThrough</code>, <code>action</code>, <code>revocationPending</code>, <code>licenseType</code>, <code>notice</code>, <code>pricingUrl</code>, and <code>termsUrl</code>. <code>valid</code> describes the signed grant, not permission under the free license. <code>commercial</code> requires verified production rights; <code>sandbox</code> identifies a test grant without production rights. <code>free</code> covers non-commercial and open-source use and a 30-day organization evaluation; commercial use beyond evaluation requires a paid license. The packaged LICENSE controls each version.

Status makes no network or vault call and exposes no credentials, complete grants, or account identifiers. Production is the default; sandbox requires explicit selection.

Development builds with local journal status add a separate <code>localErrorJournal</code> block. Released Glider 12.3.0 does not expose it. If the response ceiling omits this block, <code>localErrorJournalOmitted: true</code> reports the omission. At smaller limits, <code>statusDetailsOmitted: true</code> marks additional omitted fields. Increase <code>--max-response-chars</code> for complete status.

It reports <code>enabled</code>, nullable <code>available</code>, <code>reason</code>, resolved <code>directory</code>, <code>filePattern</code>, <code>schemaVersion</code>, retention limits, <code>writeState</code>, <code>storageFailure</code>, and <code>droppedRecords</code>. It contains cached observations, no journal contents, and performs no storage check.

<code>writeState</code> is <code>not_attempted</code>, <code>succeeded</code>, or <code>failed</code>. <code>available: null</code> means no record write has established availability. A prior successful write does not guarantee current disk access. Disabled or unavailable status does not prove that older records are absent. The existing <code>process.diagnosticsLog</code> is five-minute resource history, not error history. Results use top-level fields with success. Compact is the default; full adds responseDiagnostics. Both modes retain errors, coverage, partial state, and recovery advice.