Remote MCP (Cloud)

Connect any MCP-compatible client to Pensyve Cloud. No binary to install and no local storage to manage. Supported interactive clients authenticate through the browser; API keys remain available for unattended automation.

Prerequisites

Create a Pensyve Cloud account. For interactive clients, add the server URL and let the client discover Pensyve's OAuth metadata. The client opens browser consent when it first connects.

Connect with OAuth (Recommended)

Antigravity CLI

Install the native plugin for rules, skills, and the preconfigured server:

agy plugin install https://github.com/major7apps/pensyve/tree/main/integrations/antigravity-plugin

For MCP only:

agy mcp add pensyve https://mcp.pensyve.com/mcp

Open /mcp, select pensyve, and choose Authenticate. See the dedicated Antigravity CLI guide for local mode and migration details.

Claude Code and Codex CLI

claude mcp add --transport http pensyve https://mcp.pensyve.com/mcp
codex mcp add pensyve --url https://mcp.pensyve.com/mcp
codex mcp login pensyve

The URL-only Claude Code registration starts OAuth on first use. Codex separates server registration from the explicit login command.

GitHub Copilot CLI

copilot mcp add --transport http pensyve https://mcp.pensyve.com/mcp

Copilot starts browser OAuth when it first connects. To re-authenticate, start an interactive copilot session and run:

/mcp auth pensyve

OpenClaw

openclaw mcp add pensyve --url https://mcp.pensyve.com/mcp --transport streamable-http --auth oauth

Cursor, Cline, and Claude Desktop

Use the client's MCP settings UI or add a URL-only HTTP server:

{
  "mcpServers": {
    "pensyve": {
      "type": "http",
      "url": "https://mcp.pensyve.com/mcp"
    }
  }
}

VS Code Copilot

Add to .vscode/mcp.json:

{
  "servers": {
    "pensyve": {
      "type": "http",
      "url": "https://mcp.pensyve.com/mcp"
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "pensyve": {
      "serverUrl": "https://mcp.pensyve.com/mcp"
    }
  }
}

OpenCode

Add a remote MCP server to opencode.json:

{
  "mcp": {
    "pensyve": {
      "type": "remote",
      "url": "https://mcp.pensyve.com/mcp",
      "enabled": true
    }
  }
}

OpenCode starts OAuth automatically on first use. You can also start it explicitly:

opencode mcp auth pensyve

Continue

Continue CLI documents browser OAuth workflows; generic Continue IDE MCP documentation does not guarantee automatic OAuth for every configuration, so use a token fallback where required.

API-Key Fallback for Automation

Create a scoped key at Settings → API Keys, store it in your CI secret manager, and send it as an HTTP Bearer token. For clients that expand environment variables in request headers, the shape is:

{
  "mcpServers": {
    "pensyve": {
      "type": "http",
      "url": "https://mcp.pensyve.com/mcp",
      "headers": {
        "Authorization": "Bearer ${PENSYVE_API_KEY}"
      }
    }
  }
}

Available Tools

The remote MCP server exposes 10 tools:

Every metered tool call counts as one operation against your plan's usage pool. See Pricing for details.

For full tool parameter reference, see MCP Tools.

Verify Connection

Once connected, ask your agent to check the connection:

"What's my Pensyve status?"

The agent will call pensyve_status and return your namespace, memory counts, and health status.

Remote vs Local

Both modes expose the same 10 tool names and request parameters, so agents do not need to change prompts or workflows when switching between local and remote. pensyve_account returns mode-specific account context: unlimited self-hosted usage locally and Pensyve Cloud account information remotely.