Estimay

io.estimayPublished by estimay.ioOfficial publisherv1.4.0Updated Nov 6, 2026

Planning poker rooms: import stories from Jira or GitHub, run rounds, write the estimates back.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Estimay is a remote MCP server for planning poker: it lets an assistant import stories from Jira or GitHub, run estimation rounds and write estimates back.

What you can do
  • Import stories from Jira or GitHub into planning poker rooms
  • Run estimation rounds in those rooms
  • Write the resulting estimates back to the source tracker
When to use it
Useful when a team runs planning poker or sprint estimation and wants an assistant to pull backlog stories from Jira or GitHub, drive the rounds and push the agreed estimates back to the tracker.
Requirements
A remote streamable HTTP endpoint at estimay.io; no local package or runtime is needed. OAuth authentication is required, so the user must sign in to an Estimay account and authorize the connection. Access to the relevant Jira or GitHub projects is needed to import and write back stories.
Before you install
The server writes estimates back to Jira or GitHub, so it can change data in your trackers. It requires OAuth sign-in to an Estimay account, and story content from your Jira or GitHub projects is sent to a third-party service.

Installation

In SourceWeft

  1. Open Estimay 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.estimay%2Festimay/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": {
    "estimay": {
      "type": "http",
      "url": "https://estimay.io/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

5
  1. v1.4.0LatestNov 6, 2026
  2. v1.3.0Nov 3, 2026
  3. v1.2.0Nov 3, 2026
  4. v1.1.0Oct 29, 2026
  5. v1.0.0Oct 26, 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 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
  • 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.