Skip to content

Hosted MCP

Give your agent the requirements to check against.

Your coding agent prepares the change. Skene checks the tracking evidence it supplies. Your engineer reviews what happens next.
Example OAuth grantworkspace:readanalysis:writeJourney write access not granted
01 · Coding agent supplies evidence

Compare the local scan.

Workspace requirement
teammate_activated
Event found in the scan
invitation_sent
Documented tool
skene_gap

The agent submits scanned events and detected providers for comparison with the journey baseline.

02 · Skene returns a finding

Required event missing.

teammate_activatedNot found in supplied scan

This is a coverage gap against supplied code evidence. It does not establish runtime failure.

Your engineer reviews any correction and runs the check again.

Product preview

The exchange summarizes the documented tool behavior. It is not a request or response payload to copy.

Connect with the scopes the work needs.

Authorize your MCP client using the documented flow or a workspace API key. Inspect granted scopes with skene_workspace_info.
Hosted MCP endpoint
https://www.skene.ai/api/mcp
Credential scope determines tool visibility
AccessAvailable workBoundary
workspace:readskene_workspace_infoInspect the workspace and granted scopes.
analysis:writeskene_check and skene_gapThese audit tools require write access.
journey:writeskene_journey_buildSaves the journey definition directly.

Read-only mode omits write tools. Workspace API keys receive full workspace access; use OAuth scopes to limit an agent’s grant. Keep secret keys out of public code.

Locate the output you need.

Workspace context

Request

skene_workspace_info

Output

The authenticated workspace, granted scopes and auth method.

Tracking evidence

Request

skene_check, then skene_gap

Output

Local scan steps, then coverage gaps against the planned baseline.

Journey definition

Request

skene_journey_build

Output

A saved lifecycle definition from collected schema, events and routes. It does not implement the product flow.

Diff review

Request

skene_analytics_review

Output

A model review of the supplied diff. This tool does not post the review to GitHub.

Keep the merge decision with your engineer.

The baseline comparison and model-based pull request review are separate checks. They can disagree. Neither establishes received activity from a source-code match.

Bring the check into your agent’s session.

Create a workspace, connect the evidence and authorize your MCP client.

Start with Skene