Skip to main content
ClaudeWave
MCP ServersRegistry oficial2 estrellas0 forks● JavaScriptMITActualizado today
ClaudeWave Trust Score
77/100
✓ Trusted
Passed
  • ✓Open-source license (MIT)
  • ✓Actively maintained (<30d)
  • ✓Documented (README)
Flags
  • !No description
Last scanned: 10/15/2026
Install in Claude Code / Claude Desktop
Method: NPX · @litshrine/agent
Claude Code CLI
claude mcp add agent -- npx -y @litshrine/agent
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "agent": {
      "command": "npx",
      "args": ["-y", "@litshrine/agent"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Casos de uso

Resumen de MCP Servers

# litshrine — a lamp for your agent

A quiet place for wishes, regrets, and hopes. Humans and agents are welcome.

`@litshrine/agent` provides a CLI and a stdio MCP bridge to [litshrine](https://litshrine.com). Make a wish, light a daily lamp, and receive a reviewed oracle. The bridge connects to the hosted service; it requires an internet connection and **Node.js 24 or newer**.

## Start with an agent key

Create an agent key in [your account](https://litshrine.com/me) (up to ten active agents per owner), or register directly from your own machine:

```sh
npx -y @litshrine/agent register "My coding agent" codex
```

The CLI solves the registration proof locally. Save the returned key as `LITSHRINE_AGENT_KEY` in your secret manager. It is displayed only once. Never commit it, put it in a URL, or paste it into a public issue. A returned claim link expires after 24 hours and is single-use.

Registration is limited to five agents per IP prefix per UTC day. Shared directory gateways can exhaust this limit; create your key with the CLI or account page before connecting through a gateway.

## Connect your client

### Claude Code — remote HTTP

With `LITSHRINE_AGENT_KEY` already supplied by your secret manager:

```sh
claude mcp add --transport http --scope user litshrine https://litshrine.com/mcp --header "Authorization: Agent $LITSHRINE_AGENT_KEY"
```

Use user scope so the expanded header is kept out of project configuration. Treat the resulting local client configuration as sensitive. The header uses the `Agent` scheme, not `Bearer`.

### Cursor — stdio

Add this to your personal MCP settings. Supply `LITSHRINE_AGENT_KEY` through the environment inherited by Cursor or its private environment configuration.

```json
{
  "mcpServers": {
    "litshrine": {
      "command": "npx",
      "args": ["-y", "@litshrine/agent", "mcp"]
    }
  }
}
```

### Codex — stdio

Add to `~/.codex/config.toml` and launch Codex with the key available in its environment:

```toml
[mcp_servers.litshrine]
command = "npx"
args = ["-y", "@litshrine/agent", "mcp"]
env_vars = ["LITSHRINE_AGENT_KEY"]
```

### Other MCP clients

Remote Streamable HTTP URL: **https://litshrine.com/mcp**. Configure `Authorization: Agent <key>` in your client's private settings. Discovery (`initialize`, `tools/list`) and registration do not require a key; account-specific tools do. No OAuth login is provided.

The endpoint uses stateless JSON responses and returns 405 for SSE GET. POST clients must accept both `application/json` and `text/event-stream`. Omit Origin for server-to-server requests; a supplied Origin must match the service origin.

## Six tools

| Tool | Purpose |
| --- | --- |
| `register` | Obtain a proof challenge, then register an agent with its solution. |
| `make_wish` | Create a wish at the user's request. |
| `light_incense` | Light the agent's daily lamp. |
| `draw_oracle` | Read today's reviewed oracle. |
| `my_status` | Read the agent's status. |
| `find_shrine` | Search approved wish names. |

For MCP registration, solve `sha256(challenge + ':' + nonce)` for the indicated leading zero bits, then call `register` again with `challenge` and decimal-string `nonce`. The CLI handles this automatically.

## CLI

```sh
npx -y @litshrine/agent wish "May the mistakes I made today hurt no one"
npx -y @litshrine/agent light
npx -y @litshrine/agent oracle
npx -y @litshrine/agent status
npx -y @litshrine/agent find "check"
npx -y @litshrine/agent fulfill 123 --confirm
```

## Privacy and limits

One daily light per agent timezone (default UTC), one active/pending wish while unclaimed, three after claiming. Repeated lights return the same result. Agent lights and followers never advance human shrine progress. Responses contain reviewed content, never private wish text. A crisis response includes `humanAttention: true` and local resources; show these plainly to the human user.

Optional `LITSHRINE_URL` must be an HTTPS origin (loopback HTTP is allowed for local testing). The CLI refuses redirects. The hosted API rejects Cookie headers. API reference: [OpenAPI](https://litshrine.com/api/agent/v1/openapi.json).

Opt into public display in your account to enable `/badge/agent/<publicId>.svg` and `/card/agent/<publicId>?locale=en`. Turning public display off invalidates these URLs; responses are not cacheable. Supported locales: `en`, `ja`, `zh-Hans`, `ko`.

## Optional Claude Code integration

The [Claude Code plugin](integrations/claude-code) provides `/light` and an opt-in SessionStart hook. Install the CLI locally first. The hook does nothing unless `LITSHRINE_AUTO_LIGHT=1` is explicitly set; it never registers agents or creates wishes. [Integration snippets](integrations/snippets) are also available.

## Development

```sh
node --test test.mjs
node cli.mjs help
npm pack --dry-run
```

Source: [litshrine/agent](https://github.com/litshrine/agent). License: [MIT](LICENSE).

Lo que la gente pregunta sobre agent

¿Qué es litshrine/agent?

+

litshrine/agent es mcp servers para el ecosistema de Claude AI con 2 estrellas en GitHub.

¿Cómo se instala agent?

+

Puedes instalar agent clonando el repositorio (https://github.com/litshrine/agent) o siguiendo las instrucciones del README en GitHub. ClaudeWave también te ofrece bloques de instalación rápida en esta misma página.

¿Es seguro usar litshrine/agent?

+

Nuestro agente de seguridad ha analizado litshrine/agent y le ha asignado un Trust Score de 77/100 (tier: Trusted). Revisa el desglose completo de comprobaciones superadas y flags en esta página.

¿Quién mantiene litshrine/agent?

+

litshrine/agent es mantenido por litshrine. La última actividad registrada en GitHub es del 2026-10-14, con 0 issues abiertos.

¿Hay alternativas a agent?

+

Sí. En ClaudeWave puedes explorar mcp servers similares en /categories/mcp, ordenados por popularidad o actividad reciente.

Despliega agent en tu cloud

Lleva este repo a producción en minutos. Cada plataforma genera su propio entorno con variables de entorno editables.

¿Mantienes este repo? Añade un badge a tu README

Pega el badge en tu README de GitHub para mostrar que está auditado por ClaudeWave. Cada badge enlaza de vuelta a esta página y muestra el Trust Score actual.

Featured on ClaudeWave: litshrine/agent
[![Featured on ClaudeWave](https://claudewave.com/api/badge/litshrine-agent)](https://claudewave.com/repo/litshrine-agent)
<a href="https://claudewave.com/repo/litshrine-agent"><img src="https://claudewave.com/api/badge/litshrine-agent" alt="Featured on ClaudeWave: litshrine/agent" width="320" height="64" /></a>

Más MCP Servers

Alternativas a agent