My Fordyce

com.fordycecgPublished by fordycecg.comOfficial publisherv2.63.0Updated Nov 4, 2026

A hosted backlog coding agents claim work from: one ticket per agent, finished work back to review.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Hosted backlog that coding agents claim work from: one ticket per agent, with finished work sent back to review.

What you can do
  • Connect an assistant to a hosted backlog where coding agents claim tickets.
  • Hand out one ticket per agent so parallel agents do not collide.
  • Return finished work to a review step.
  • Sign in with OAuth, or authenticate with an API key sent as a Bearer token.
When to use it
Useful when several coding agents work from a shared backlog and you want each to pick up a distinct ticket and hand results back for review, rather than coordinating work by hand.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package. OAuth sign-in is the default, or an API key minted on the provider's Connect page, sent in the Authorization header as a Bearer token. Network access to the hosted service.
Before you install
Requires an account and credentials: the Authorization header carries either an OAuth session or an API key. The server writes to a shared backlog and moves work into review, so agent actions change shared state. No tool list is published, so confirm what it can modify before connecting.

Installation

In SourceWeft

  1. Open My Fordyce 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.fordycecg%2Fmy-fordyce/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": {
    "my-fordyce": {
      "type": "http",
      "url": "https://myfordyce.fordycecg.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

8
  1. v2.63.0LatestNov 4, 2026
  2. v2.62.2Oct 20, 2026
  3. v2.62.1Oct 14, 2026
  4. v2.62.0Oct 4, 2026
  5. v2.61.0Sep 29, 2026
  6. v2.49.0Sep 21, 2026
  7. v2.43.0Sep 18, 2026
  8. v2.26.2Sep 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 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.