Howwe

io.howwePublished by howwe.ioOfficial publisherv0.57.0Updated Nov 4, 2026

Read and update your Howwe strategy: initiatives, MIGs, milestones, activities and teams.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote Howwe server that lets an assistant read and update strategy data such as initiatives, MIGs, milestones, activities and teams.

What you can do
  • Read strategy data: initiatives, MIGs, milestones, activities and teams.
  • Update existing strategy records such as initiatives, milestones, activities and teams.
  • No individual tools are listed in the registry entry, so the exact read and write operations are not documented here.
When to use it
Useful when your team keeps its strategy, initiatives and milestone tracking in Howwe and you want an assistant to look up or update that data without switching apps.
Requirements
A remote endpoint at api.howwe.io over streamable HTTP; no packages or environment variables are declared. Authentication is OAuth and required, so a Howwe account with access to the relevant workspace is needed.
Before you install
The server can update strategy records, so assistant actions may change initiatives, milestones, activities or teams. Access is granted through OAuth to your Howwe account, so review the scopes you approve. The registry entry lists no tools, so confirm exactly what it can read or modify before connecting.

Installation

In SourceWeft

  1. Open Howwe 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.howwe%2Fhowwe/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": {
    "howwe": {
      "type": "http",
      "url": "https://api.howwe.io/v1/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

3
  1. v0.57.0LatestNov 4, 2026
  2. v0.54.0Oct 29, 2026
  3. v0.50.0Oct 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.