LogRack

ai.lograckPublished by lograck.aiOfficial publisherv0.1.0Updated Oct 27, 2026

Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

LogRack is a remote MCP server providing shared memory for AI tools, so assistants can read and write tasks, notes and context across tools.

What you can do
  • Read and write shared tasks, notes and context over MCP.
  • Share the same memory across multiple AI tools that connect to the service.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when several AI tools or assistants should work from one shared store of tasks, notes and context instead of each keeping its own state.
Requirements
A remote MCP endpoint at mcp.lograck.ai over streamable HTTP. OAuth authentication is required, so a LogRack account is needed. No environment variables or headers are declared.
Before you install
The service stores tasks, notes and context centrally and shares them across connected tools, so anything written may be visible to every tool authorized on the account. OAuth grants access to that shared data; review which tools you connect and what they write.

Installation

In SourceWeft

  1. Open LogRack 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/ai.lograck%2Flograck/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": {
    "lograck": {
      "type": "http",
      "url": "https://mcp.lograck.ai/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. v0.1.0LatestOct 23, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.