Specky

io.github.fathyshalabyPublished by GitHub account fathyshalabyv0.1.0Updated Oct 24, 2026

Turn raw customer feedback into evidence-cited specs (free, no key) plus 16 PM tools.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Turns raw customer feedback into evidence-cited product specs, alongside a set of product-management tools.

What you can do
Specky is a remote MCP server that converts raw customer feedback into product specifications where claims are backed by cited evidence. The registry description also mentions a set of 16 product-management tools, though no individual tool names or schemas are listed. It is reached over streamable HTTP at a hosted endpoint rather than run locally.
When to use it
Consider it when you want an assistant to help turn collected customer feedback into structured specs, or when you want product-management helpers available in the same session. It is a hosted service, so it suits users who prefer not to install or run anything locally.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. The manifest declares no authentication, no environment variables and no headers, and no package install is needed.
Before you install
The description states it is free and needs no key, but the manifest lists no tools, so the exact actions it can take are not documented here. Feedback you submit is sent to a third-party hosted service; avoid sending confidential customer data unless you have verified how it is handled.

Installation

In SourceWeft

  1. Open Specky in the dashboard and add it to a workspace.
  2. 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.fathyshalaby%2Fspecky/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.

{
  "mcpServers": {
    "specky": {
      "type": "http",
      "url": "https://www.specky.space/api/mcp"
    }
  }
}

Tools

1

feedback_to_spec

Feedback To Spec

Turn one piece of raw customer feedback (a Slack message, review, support ticket, or email) into a prioritized, evidence-backed product insight and a PRD problem statement — with the exact verbatim quotes that justify it. No account or API key required. Rate-limited per caller.

Parametersfeedbackrequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% 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 listedRequired15 pts
  • 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.