featureloom

com.featureloomPublished by featureloom.comOfficial publisherv1.0.0Updated Nov 8, 2026

Requirements and backlog as living markdown plans, handed whole to your coding agent over MCP.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Featureloom serves requirements and backlog as living markdown plans that an assistant can hand whole to a coding agent over MCP.

What you can do
  • Retrieve requirements and backlog items kept as living markdown plans
  • Hand a complete plan to a coding agent in one piece over MCP
  • Keep planning documents current as the source of truth for work
  • No tool list is published, so exact operations are not documented
When to use it
Consider it when your requirements and backlog live as markdown plans and you want an assistant or coding agent to work from the whole plan rather than fragments.
Requirements
A remote MCP endpoint at mcp.featureloom.com using streamable HTTP, with OAuth authentication required. No environment variables, headers or packages are declared.
Before you install
OAuth access is required, so the server can reach your planning content; review what scopes it requests. No tool list is published, so it is unclear whether the assistant can only read plans or also change them.

Installation

In SourceWeft

  1. Open featureloom 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/com.featureloom%2Ffeatureloom/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": {
    "featureloom": {
      "type": "http",
      "url": "https://mcp.featureloom.com/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.0LatestNov 8, 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.