Skene
Product
Pricing
Docs
Blog
About
Log In
ProductPricingDocsBlogAbout
Log In
Skene subpage background texture

From an earlier version of Skene. See the current product →

  1. Home
  2. /
  3. Resources
  4. /
  5. Docs
  6. /
  7. skene CLI
CLI docs

MCP Server

Navigation

skene CLI

  • Overview
  • Installation
  • Quickstart
  • Analyze
  • Plan
  • Build
  • Push
  • Login
  • Status
  • Features
  • Chat
  • LLM Providers
  • Configuration
  • MCP Server
  • CLI Reference
  • Python API
  • Manifest Schema
  • Troubleshooting

Resources

  • Playbooks
  • Glossary

skene CLI

  • Overview
  • Installation
  • Quickstart
  • Analyze
  • Plan
  • Build
  • Push
  • Login
  • Status
  • Features
  • Chat
  • LLM Providers
  • Configuration
  • MCP Server
  • CLI Reference
  • Python API
  • Manifest Schema
  • Troubleshooting

Resources

  • Playbooks
  • Glossary

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, deploy status, journey data, analytics audit flows, and push validation.

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.

ToolDescription
skene_workspace_infoReturns the authenticated workspace and granted scopes for the MCP credential.
skene_get_deploy_statusReturns latest workspace deploy state and artifact snapshot.
skene_get_growth_intelligenceReturns workspace intelligence snapshot (funnel, waterfall, daily pulse, loop matrix, ICP).
skene_get_journeyReturns journey canvas data with stages, milestones, levers, triggers, connectors, and usage overlays.
skene_usersManages analytics audit personas (create, list, update).
skene_initInitializes an analytics audit with app context and persona information.
skene_gapGenerates and stores the final analytics gap report for an audit.
skene_validate_pushDry-run validates push payload content and returns updated paths and would-change state.

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.

Local stdio MCP (advanced path)

Skene also supports local stdio MCP via the CLI for local-repo workflows. That mode is separate from the hosted endpoint above.

  • Hosted endpoint docs: /resources/docs/cloud/mcp
  • Local CLI docs: /resources/docs/skene

Next Steps

  • Skene Cloud MCP - Full hosted MCP guide
  • Workspace API keys - Manage API keys and access
  • skene CLI docs - Local CLI and stdio workflows
Previous← ConfigurationNextCLI Reference →
Skene

Product

How it worksFeaturesArchitectureIntegrationsSecurityPricing

Resources

DocumentationGlossaryPlaybooksBlog

Company

AboutOpen sourceContactPrivacyTerms
© 2026 Skene. All rights reserved.
Privacy PolicyTerms of Service
Skene