SaveHQ

app.savehqPublished by savehq.appOfficial publisherv1.0.0Updated Oct 24, 2026

Free save layer for AI apps: save links to a person's SaveHQ board and search it, with permission.

VerifiedStreamable HTTPWeb executableKnowledge & Memory

Overview

AI-generated overview

Lets an assistant save links to a person's SaveHQ board and search that board, with the user's permission.

What you can do
SaveHQ is a remote MCP server that acts as a save layer for AI apps. According to the registry description, it lets an assistant save links to a person's SaveHQ board and search that board, with permission. No individual tools are listed in the supplied manifest, so the exact tool names and parameters are not documented here.
When to use it
Consider it when you want an assistant to capture links it encounters into a personal SaveHQ board and later look them up again. It is aimed at saving and retrieving links rather than general browsing or file management.
Requirements
It runs as a remote endpoint at savehq.app over streamable HTTP, so no local runtime or package is needed. Authentication is OAuth and is required. No environment variables or headers are declared.
Before you install
It is a remote hosted service, so saved links and search queries go to SaveHQ rather than staying on your machine. Access is granted through OAuth, so review the permissions requested during sign-in. The supplied description mentions saving and searching only; no destructive actions are described.

Installation

In SourceWeft

  1. Open SaveHQ 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/app.savehq%2Fsavehq/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": {
    "savehq": {
      "type": "http",
      "url": "https://savehq.app/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.0LatestOct 10, 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.