Liminary

io.liminary.apiPublished by api.liminary.ioOfficial publisherv1.0.1Updated Oct 24, 2026

Your AI's memory for what you actually know: recall across your documents, notes, and meetings

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Liminary gives an assistant recall across your own documents, notes, and meetings through a hosted MCP endpoint.

What you can do
According to the registry description, the server acts as memory for what you actually know, letting an assistant recall information across your documents, notes, and meetings. It is a remote streamable HTTP service, and no individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Worth considering when you want an assistant to draw on your existing written material and meeting records instead of only the current conversation. Less useful if you have no such content connected or prefer to keep personal notes out of a third-party service.
Requirements
Remote MCP server reached over streamable HTTP at a hosted endpoint; no local package or runtime is needed. OAuth authentication is required. No environment variables or headers are declared.
Before you install
Authentication is OAuth and required, so the assistant gains access to a connected account holding personal documents, notes, and meeting content; review what scopes are granted and whether that content is sent to a third-party service before connecting. No tools are listed in the manifest, so capabilities cannot be verified in advance.

Installation

In SourceWeft

  1. Open Liminary in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.liminary.api%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "liminary": {
      "type": "http",
      "url": "https://api.liminary.io/api/mcp/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.