Troth

io.github.thegrenadinekid25Published by GitHub account thegrenadinekid25v0.22.0Updated Oct 27, 2026

AI-powered spec-to-task decomposition and execution orchestration for coding agents.

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Troth is a remote MCP endpoint that turns specifications into decomposed tasks and orchestrates their execution for coding agents.

What you can do
  • Break a specification down into smaller tasks for a coding agent.
  • Orchestrate the execution of those tasks as the agent works through them.
  • No tool list is published, so the exact operations available to an assistant are not documented in the supplied material.
When to use it
Consider it when you want a coding agent to work from a written spec and need the work split into tasks and sequenced rather than handled in one pass.
Requirements
A remote MCP endpoint at mcp.usejig.dev over streamable HTTP; no packages, environment variables or headers are declared. No authentication is declared, so no credentials appear to be needed.
Before you install
The server is described as orchestrating execution of coding tasks, which may involve running or changing code in your project; review what it does before pointing it at a real repository. No tool list, README or instructions are published, so its behaviour and data handling cannot be verified from this listing.

Installation

In SourceWeft

  1. Open Troth 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.thegrenadinekid25%2Ftroth/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": {
    "troth": {
      "type": "http",
      "url": "https://mcp.usejig.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.22.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.