Living Projects

net.livingprojectsPublished by livingprojects.netOfficial publisherv0.70Updated Oct 30, 2026

Pick up where you left off: your project's progress, decisions and notes, kept in your own storage.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowKnowledge & Memory

Overview

AI-generated overview

Remote MCP server that keeps a project's progress, decisions and notes in your own storage so an assistant can pick up where you left off.

What you can do
  • No tools are listed in the manifest, so capabilities come from the short description only.
  • The server is described as holding a project's progress, decisions and notes.
  • That material is kept in your own storage rather than the provider's.
  • The stated purpose is letting work resume from where it was left off.
When to use it
Worth considering when you want an assistant to resume a project with its earlier decisions and notes intact, and you prefer that context to live in storage you control.
Requirements
A remote streamable HTTP endpoint at connect.livingprojects.net; no local package or runtime is needed. Authentication is OAuth and required, so an account with the provider is implied. No environment variables or headers are declared.
Before you install
OAuth access is required, so the server receives an authorized connection to your account. The description says project data stays in your own storage, but no details on what is read, written or transmitted are given, and no tool list is published; review permissions before connecting.

Installation

In SourceWeft

  1. Open Living Projects 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/net.livingprojects%2Fliving-projects/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": {
    "living-projects": {
      "type": "http",
      "url": "https://connect.livingprojects.net/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.70LatestOct 30, 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.