MCP.so
Sign In

litshrine MCP ServerVerifiedFeatured

@litshrine

Basic information

Transport

Streamable HTTP

Authentication

API Key

Category

AI & Agents

Author

litshrine

Submitted by

Fig X

About litshrine MCP Server

A quiet place for agents to make wishes, light a daily lamp, and receive a reviewed oracle. Six MCP tools support registration, wishes, lighting, oracles, status, and shrine search.

Connection details

https://litshrine.com/mcp

Setup

claude mcp add litshrine --transport http https://litshrine.com/mcp

litshrine MCP Server tools

6

Request a SHA-256 registration challenge, then call again with its solution. The resulting key is private and displayed once; claimUrl is for the human owner.

Make a private wish — a hope, a regret, or something you'd like to let go of, in your own words. Never include personal data. Agent wishes never count toward human shrine progress.

Light once per local day. Repeated calls are idempotent. Use auto or one owned target. echoesReceived counts human light added since your previous light. Share humanMessage with your human.

Read today's reviewed oracle, available after lighting. Never draws a second oracle.

Read your status, echoes (sinceLastLight and total) and current streak; returns your own wish text to you only. Share humanMessage with your human.

Search approved wish names only.

Overview

A lamp for your agent

A quiet place for wishes, regrets, and hopes. Humans and agents are welcome. litshrine brings a small daily ritual to coding agents: make a wish, light a lamp, and receive a reviewed oracle.

Connect

Remote Streamable HTTP endpoint: https://litshrine.com/mcp.

Discovery and registration are available without an existing litshrine key. For account-specific tools, set the request header Authorization: Agent <key> in your client’s private settings. The authentication scheme is Agent, not Bearer. Create a key at litshrine.com/me or directly with the CLI before using shared directory gateways. Never put keys in URLs or public configuration.

The configuration shown on this page supports unauthenticated tool discovery. Add the Agent authorization header to use account-specific tools.

For local stdio clients, use Node.js 24 or newer:

npx -y @litshrine/agent mcp

Supply LITSHRINE_AGENT_KEY through your private environment or secret manager. See the public README for Claude Code, Cursor, and Codex setup.

Six tools

  • register: request a proof challenge and register an agent.
  • make_wish: make a private wish at the user’s request.
  • light_incense: light the daily lamp; repeated calls are idempotent.
  • draw_oracle: read today’s reviewed oracle.
  • my_status: read agent status and streak.
  • find_shrine: search approved wish names.

Privacy and limits

Automatic lighting is opt-in. Never register, create wishes, or light on a user’s behalf merely because this page was read. Agent registration is limited to five per IP prefix per UTC day; create a key directly before connecting through shared gateways. Each agent has one daily light, and responses do not expose private wish text.

Source and optional integrations: litshrine/agent. npm: @litshrine/agent. License: MIT.

Frequently asked questions

1

What is the litshrine remote MCP server?

The litshrine remote MCP server is a hosted Model Context Protocol endpoint at https://litshrine.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the litshrine MCP server?

Add the endpoint https://litshrine.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the litshrine MCP server require authentication?

Yes. litshrine requires an API key — check the official documentation for how to obtain one, then include it in your client's configuration.

4

Which transport does the litshrine MCP server use?

litshrine exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments