Getting Started with the Sliplane MCP server

Connect your AI coding tools to Sliplane using the Model Context Protocol (MCP). The Sliplane MCP server is a hosted, remote MCP server available at:

https://mcp.sliplane.io

What is the Sliplane MCP server?

The Sliplane MCP server gives compatible AI clients access to the functionality of the Sliplane API. It uses Streamable HTTP and supports OAuth, so compatible clients can open the Sliplane authorization flow and receive a scoped API token without requiring you to copy an API key into their configuration.

You can use it to:

Manage deployments
Access project information
Monitor application status
Execute deployment operations

Authentication

OAuth is the recommended authentication method. When your MCP client connects, it opens Sliplane in your browser so you can sign in and authorize access.

Use these OAuth settings if your client asks for them:

Client ID: sliplane-mcp
Scope: full
Client secret: None

API keys remain supported for clients that do not support OAuth. You can create an API key in your Sliplane team settings and send it as a bearer token.

Setup

Choose your MCP client below. The hosted server requires no local installation or self-hosting.

Add the Sliplane MCP server with its OAuth client ID:

claude mcp add --transport http \
  --client-id sliplane-mcp \
  sliplane https://mcp.sliplane.io

Start Claude Code, enter /mcp, and complete the browser authorization flow.

Create an API key, then send it as a bearer token:

claude mcp add --transport http \
  -H "Authorization: Bearer yourapikeyhere" \
  sliplane https://mcp.sliplane.io

Codex

OAuth
API key

Add the Sliplane MCP server with OAuth:

codex mcp add sliplane \
  --url https://mcp.sliplane.io \
  --oauth-client-id sliplane-mcp

Complete the browser authorization flow when Codex connects to the server.

Create an API key, then send it as --bearer-token-env-var:

export SLIPLANE_API_KEY=yourapikeyhere

codex mcp add sliplane \
  --url https://mcp.sliplane.io \
  --bearer-token-env-var SLIPLANE_API_KEY

Cursor

Add one of the following configurations to your project-specific or global .cursor/mcp.json file:

OAuth
API key

{
  "mcpServers": {
    "sliplane": {
      "url": "https://mcp.sliplane.io",
      "auth": {
        "CLIENT_ID": "sliplane-mcp",
        "scopes": ["full"]
      }
    }
  }
}

When Cursor connects, complete the OAuth authorization flow.

{
  "mcpServers": {
    "sliplane": {
      "url": "https://mcp.sliplane.io",
      "headers": {
        "Authorization": "Bearer yourapikeyhere"
      }
    }
  }
}

opencode

OAuth
API key

Run the interactive setup:

opencode mcp add

Enter the following values when prompted:

┌  Add MCP server
│
◇  Enter MCP server name
│  sliplane
│
◇  Select MCP server type
│  Remote
│
◇  Enter MCP server URL
│  https://mcp.sliplane.io
│
◇  Does this server require OAuth authentication?
│  Yes
│
◇  Do you have a pre-registered client ID?
│  Yes
│
◇  Enter client ID
│  sliplane-mcp
│
◇  Do you have a client secret?
│  No

Then authenticate with Sliplane:

opencode mcp auth sliplane

Create an API key, then:

opencode mcp add sliplane \
  --url https://mcp.sliplane.io \
  --header "Authorization=Bearer yourapikeyhere"

Visual Studio Code

VS Code can connect using an API key. Create .vscode/mcp.json in your repository:

{
  "servers": {
    "sliplane": {
      "type": "http",
      "url": "https://mcp.sliplane.io",
      "headers": {
        "Authorization": "Bearer yourapikeyhere"
      }
    }
  }
}

Other MCP clients

For clients not listed above, use the following connection settings:

URL: https://mcp.sliplane.io
Transport: Streamable HTTP
OAuth client ID: sliplane-mcp
OAuth scope: full
OAuth client secret: None

Use the authentication settings that match your client:

OAuth
API key

OAuth client ID: sliplane-mcp
OAuth scope: full
OAuth client secret: none

Authorization: Bearer yourapikeyhere