Lycatra

com.lycatrav0.2.0Updated Oct 6, 2026

Connect agents to Lycatra knowledge, memory, collaboration, schedules, notifications, and teams.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Connects an AI assistant to a Lycatra account for knowledge, memory, teams, schedules, notifications, and chat.

What it does
Lycatra is a hosted MCP server that gives an assistant access to account-stored resources: agents, a wiki, memory, schedules, notifications, teams, Matrix chat, vault metadata, and a browser that runs inside agents. It also offers a CLI for local or cloud shell work, such as running commands inside agents and inspecting notification subscriptions. Apps connect to one hosted endpoint and sign in once with OAuth.
When to use it
Worth adding when you want an assistant to work with your Lycatra knowledge base, memory, team collaboration, schedules, and notifications from clients such as Claude, ChatGPT, Codex, Cursor, VS Code, Gemini CLI, Goose, or LM Studio. It is aimed at users who already keep this material in Lycatra and want it available across several MCP clients.
Requirements
A remote MCP endpoint reached over the network; no local package is declared. A Lycatra account and OAuth sign-in are required, and the app only sees what the account can access. Some clients need developer mode or a plugin marketplace step. The optional CLI installs via a shell script and may need local runtime capabilities for ports and child processes.
Before you install
The server exposes account data including wiki, memory, teams, Matrix chat, vault metadata, and notifications, so review what each client may read. Writes, deletions, and anything visible to other people still depend on the app's permission prompts. The CLI can be installed by an agent that runs shell commands, and notification subscription resync with the --yes flag skips a parked or cancelled event without retrying it.

Installation

In SourceWeft

  1. Open Lycatra in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

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

README

Lycatra plugin

Lycatra for Claude, ChatGPT, Codex, Cursor, VS Code, and any other app that speaks MCP: your agents, wiki, memory, teams, schedules, notifications, Matrix chat, and vault, in one sign-in.

Install

Every app below connects to https://lycatra.com/api/mcp and asks you to sign in to Lycatra once. One-click buttons for every app are on lycatra.com/connect.

Claude

Claude on the web, desktop, and mobile, and Cowork.

Recommended: the plugin, with skills:

  1. In Claude, open Customize, then Plugins, then Add marketplace.
  2. Enter Lycatra/lycatra-plugin and turn on Sync automatically.
  3. Install Lycatra, then connect it when Claude asks you to sign in.

A plugin added here also appears in Claude Code when you sign in with the same account.

Team and Enterprise plans: an organization owner adds Lycatra, then members connect it.

ChatGPT

ChatGPT on the web and desktop.

Developer mode:

  1. In ChatGPT, open Settings, then Security and login, and turn on Developer mode.
  2. Open chatgpt.com/plugins, choose the plus button, and enter https://lycatra.com/api/mcp.
  3. Sign in to Lycatra when ChatGPT asks.

Until Lycatra is in the ChatGPT directory, adding it needs developer mode, which depends on your plan.

Claude Code

Lycatra tools, plus the Lycatra CLI for work that needs your computer.

sh
claude plugin marketplace add Lycatra/lycatra-pluginclaude plugin install lycatra@lycatra

Turn on updates in /plugin, Marketplaces, then Enable auto-update. lycatra setup does this for you.

Codex

The Codex CLI, the Codex app, and ChatGPT desktop.

sh
codex plugin marketplace add Lycatra/lycatra-plugincodex plugin add lycatra@lycatra

Codex IDE extension (tools only):

sh
codex mcp add lycatra --url https://lycatra.com/api/mcp

Cursor

Lycatra tools in Cursor's agent.

VS Code

GitHub Copilot in VS Code.

GitHub Copilot CLI

Lycatra in the Copilot command line.

sh
copilot plugin marketplace add Lycatra/lycatra-plugincopilot plugin install lycatra@lycatra

Gemini CLI

Lycatra tools as a Gemini CLI extension.

sh
gemini extensions install https://github.com/Lycatra/lycatra-plugin --auto-update

Goose

Lycatra tools as a Goose extension.

LM Studio

Lycatra tools for local models.

Any other MCP client

Add the MCP server URL. It signs in with OAuth.

Set up every agent add-mcp finds:

sh
npx add-mcp https://lycatra.com/api/mcp

The Lycatra CLI

Agents that can run shell commands install it themselves the first time they need your computer, for example to run a command inside one of your agents. To install it yourself:

sh
curl -fsSL https://lycatra.com/install.sh | bash
powershell
irm https://lycatra.com/install.ps1 | iex

How it works

Every app talks to Lycatra's hosted MCP server for anything stored in your account: agents, wiki, memory, schedules, notifications, teams, Matrix, vault metadata, and a browser that runs inside your agents. You sign in once with Lycatra's OAuth prompt, and the app only sees what your account can access.

Hosted MCP and the Lycatra CLI are both supported interfaces. An authorized local or cloud shell can use the checksum-verified CLI for the same account operations. Local ports and child processes additionally need suitable runtime capabilities. Ordinary hosted tools do not require a personal computer.

Cloud event delivery is negotiated with the receiving host when supported by the server. It continues independently of a CLI shell. The CLI can inspect and manage owner-authorized subscriptions, but cannot manufacture a host callback or wake a chat by name. Start with lycatra notify targets doctor --json for read-only diagnosis. Local notify wake adapters remain separate.

For explicit cloud-agent enrollment, use the selected environment's /api/mcp/cloud resource returned by notify targets connect. Compatible hosts discover its starter scopes and follow OAuth enrollment and consent. The normal /api/mcp resource retains human-account behavior. Cloud event support still requires qualification in the receiving host.

Explicitly approved notify events subscriptions resync <id> --yes skips one parked or cancelled head event and reports the skipped sequence and new cursor. It does not retry that event or change subscription pause or lease expiry.

Beta uses dev and stable uses production throughout installation, login and updates. Each CLI profile has separate credentials and update state. Provider credential setup for local coding harnesses is optional, separate from login.

Your app's normal permission prompts still apply to writes, deletions, and anything visible to other people.

Support

Source: README.md at commit 3f6a24e

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.2.0LatestOct 6, 2026