AppHandoff

io.github.TeamK2KPublished by GitHub account TeamK2Kv1.0.2Updated Oct 24, 2026

Milestones, handoff tickets, project context, and deploy signals for AI-built apps over MCP.

The publisher's own server: Agentic Pipeline

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Gives an assistant access to milestones, handoff tickets, project context, and deploy signals for AI-built apps.

What you can do
AppHandoff exposes project workflow information for AI-built apps over MCP. According to its registry description, it covers milestones, handoff tickets, project context, and deploy signals. The manifest does not list individual tools, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs to work with project milestones, handoff tickets, or deployment signals for an app built with AI assistance, and when that information should be reachable during a conversation rather than looked up manually.
Requirements
A remote MCP endpoint at using streamable HTTP. OAuth authentication is required; no environment variables or headers are declared. Network access to the endpoint is needed.
Before you install
Access is granted through OAuth, so the assistant may read project data held by the service. The description mentions deploy signals, which could relate to deployment activity; review what the connection is permitted to see or change before authorizing it.

Installation

In SourceWeft

  1. Open AppHandoff 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.github.TeamK2K%2Fapphandoff/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": {
    "apphandoff": {
      "type": "http",
      "url": "https://api.apphandoff.com/mcp"
    }
  }
}

README

This repository has no README.

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.2LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Agenticpipeline integrations