Skene MCP is a hosted MCP endpoint for coding agents. It does not replace Cursor or Claude Code. It plugs into them and gives access to workspace context, Lifecycle journey data, the tracked events inventory, analytics audit flows, and tracking plan Check results.
Endpoint:
https://www.skene.ai/api/mcp
Authentication:
Pass your workspace API key in the X-API-Key header (see config below).
Quick setup
1) Create a workspace API key
Open your workspace in Skene:
Settings -> API keys
Create or copy a key for MCP usage.
2) Add the MCP server in your client
Use this config pattern:
{
"mcpServers": {
"skene": {
"url": "https://www.skene.ai/api/mcp",
"headers": {
"X-API-Key": "your-workspace-api-key"
}
}
}
}
3) Verify
Call skene_workspace_info from your MCP client.
If credentials and scopes are valid, the response includes workspace id, workspace slug, granted scopes, and auth method.
Tools
The hosted Skene MCP server currently exposes these tools, grouped by the Cloud product area they belong to. The Skene MCP page in your workspace shows the same grouping (Flows has no tools yet).
| Tool | Group | Description |
|---|---|---|
skene_workspace_info | Connection | Returns the authenticated workspace and granted scopes for the MCP credential. |
skene_journey_analyse | Lifecycle | Starts a Lifecycle rebuild and returns which schema, events, and routes to collect. |
skene_journey_build | Lifecycle | Builds and saves the Lifecycle definition from the collected schema, events, and routes. |
skene_get_journey | Lifecycle | Returns Lifecycle canvas data with stages, steps, levers, triggers, connectors, and usage overlays. |
skene_view_journey | Lifecycle | Opens an interactive Lifecycle map for exploring stages and steps. |
skene_get_tracking_events | Events | Lists tracked events in the same order as the Events page, with status, files, and mapped steps. |
skene_check | Events | Starts an analytics scan and returns the scan steps for the agent to run locally. |
skene_gap | Events | Compares scanned events and providers against the Lifecycle baseline and returns coverage gaps. |
skene_ack | Events | Records whether flagged events are wired, deferred, or rejected, so later scans skip handled gaps. |
skene_analytics_review | Events | Reviews a pull request diff for tracking regressions. It does not post to GitHub. |
skene_feature_check | Plans | Checks every active tracking plan for success metric movement, goal status, and Check learning. |
Scope and access
Tool visibility depends on scopes granted to the MCP token.
- Read tools require read scopes.
- Write tools require write scopes.
- In read-only mode, write tools are filtered out.
Next Steps
- Workspace API keys - Manage API keys and access
- GitHub integration - PR reviews and tracking checks