# Lycatra [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/Lycatra/lycatra-plugin  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/lycatra

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

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "lycatra": {
    "url": "https://lycatra.com/api/mcp"
  }
}
```

## Documentation

## What the Lycatra MCP server does

The Lycatra MCP server gives compatible AI applications access to information and services stored in a Lycatra account. Supported areas include agents, wiki content, memory, schedules, notifications, teams, Matrix chat, vault metadata, and a browser that runs inside agents. The account determines which resources the connected application can see.

This setup is intended for agents that need to retrieve or update shared information, coordinate with teams, work with schedules and notifications, or use Lycatra collaboration resources. Normal permission prompts in the host application still apply to writes, deletions, and actions visible to other people.

## How it works

The Lycatra MCP server is hosted at `https://lycatra.com/api/mcp`. An MCP client connects to that URL and asks the user to authenticate with Lycatra through OAuth. After sign-in, the client accesses operations allowed by the connected account rather than using a local database or a separately configured API key.

A second interface is the Lycatra CLI. Authorized local or cloud shells can use the checksum-verified CLI for account operations, while ordinary hosted tools do not require a personal computer. Local ports and child processes need suitable runtime capabilities.

Event delivery is negotiated with the receiving host when that host supports it. Cloud delivery can continue independently of a CLI shell. The CLI can inspect and manage owner-authorized subscriptions, but it cannot create a host callback or wake a chat by name. Cloud-agent enrollment uses an environment-specific `/api/mcp/cloud` resource returned by `notify targets connect`; the normal `/api/mcp` resource keeps its human-account behavior.

## Setup and configuration

Connect a client to the hosted MCP URL, then complete the Lycatra sign-in prompt. The repository documents installation paths for Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, GitHub Copilot CLI, Gemini CLI, Goose, LM Studio, and other MCP clients. The Lycatra connection page provides client-specific setup links.

For command-line installation, use the repository's marketplace commands for Claude Code, Codex, or GitHub Copilot CLI, or install the Gemini CLI extension from the repository URL. The generic option is:

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

The separate CLI can be installed with the Unix shell script or PowerShell installer. Beta and stable environments use separate installation, login, and update paths, and each CLI profile has its own credentials and update state. Provider credentials for local coding harnesses are optional and separate from Lycatra login.

## Tools and capabilities

The Lycatra MCP server exposes access to:

- Agents and wiki content
- Account memory
- Teams and collaboration data
- Schedules and notifications
- Matrix chat
- Vault metadata
- An in-agent browser
- Notification targets and event subscriptions where the host supports the required flow

The CLI also provides local command-line access for tasks that require the user's computer. A read-only notification diagnosis starts with `lycatra notify targets doctor --json`. Explicit event resynchronization requires approval and reports the skipped sequence and new cursor without retrying the skipped event.

## Limitations and notes

Cloud event features depend on qualification and support in the receiving host. Local notification wake adapters are separate from cloud event delivery. The CLI cannot manufacture callbacks or wake a conversation by name. Operations affecting other people or changing account data remain subject to the host application's permission prompts and the connected account's access rights.

_Full upstream README: https://allmcps.com/mcp/lycatra/readme_