Stipp

app.stippPublished by stipp.appOfficial publisherv1.0.0Updated Oct 27, 2026

Notes and actions in one app. Let Claude or ChatGPT read and update them.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Stipp is a remote MCP server that lets an AI assistant read and update the notes and actions kept in the Stipp app.

What you can do
  • Read notes and actions stored in Stipp
  • Update existing notes and actions
  • Work with notes and actions together in one app, as described by the provider
  • No tool list is published, so the exact operations are not documented
When to use it
Worth adding if you keep notes and to-do style actions in Stipp and want an assistant to consult or update them while you work, instead of copying content back and forth.
Requirements
A remote MCP endpoint at my.stipp.app; no local package or runtime is needed. A Stipp account with OAuth sign-in is required. Network access to the endpoint.
Before you install
The assistant can update your notes and actions, so changes may overwrite or alter existing content. Access is granted through OAuth to your Stipp account; review the permissions requested at sign-in. No tool list is published, so confirm what it can read and change before relying on it.

Installation

In SourceWeft

  1. Open Stipp 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.stipp%2Fstipp/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": {
    "stipp": {
      "type": "http",
      "url": "https://my.stipp.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.0LatestSep 25, 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.