Priowise

io.github.priowisePublished by GitHub account priowisev1.0.0Updated Oct 25, 2026

Live access to your product strategy: scored roadmap, decisions, PRDs, guarded status write-back.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Priowise gives an assistant live access to your product strategy: a scored roadmap, decisions and PRDs, with guarded status write-back.

What you can do
Read your product strategy data, including the scored roadmap, decisions and PRDs, so the assistant can answer questions and draft work from current material rather than stale copies. Write status updates back to Priowise, subject to the server's guards. The manifest lists no individual tools, so the exact set of operations is not documented here.
When to use it
Useful when you want an assistant to work from your live product strategy — reviewing roadmap priorities, referencing past decisions or PRDs, or keeping status current — instead of pasting documents into the chat.
Requirements
A remote MCP endpoint at priowise.com reached over streamable HTTP. OAuth authentication is required, so you need a Priowise account and must complete the sign-in flow. No environment variables or headers are declared.
Before you install
The server can write status changes back to your product strategy, so review what the assistant is about to change before approving it. Access is granted through OAuth to your Priowise account, so connect only clients you trust. Your product strategy content is sent to the assistant's model provider.

Installation

In SourceWeft

  1. Open Priowise 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.priowise%2Fpriowise/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": {
    "priowise": {
      "type": "http",
      "url": "https://www.priowise.com/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 11, 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.