gittr-mcp

importRemoteToBridge

Instructions

Copy a Git URL onto the bridge. With the owner key, an existing forge repo is updated to the forge commits (history kept). Does not publish the Nostr card — use mirrorRepo for the same result as the website Push. Do not use pushToBridge to sync a forge. If the URL returns 403, do not retry it and do not pass a different URL to change source: this force-updates the gittr branches to match the URL. Read the existing bare repo with bridgeListFiles instead. Leaving a dead forge is the website sidebar If this git host is gone, not this tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cloneUrl": "<cloneUrl>",
      "ownerPubkey": "<ownerPubkey>",
      "repo": "<repo>"
    },
    "name": "importRemoteToBridge"
  }
}

Input Schema

Name	Required	Description	Default
`repo`	Yes
`cloneUrl`	Yes
`bridgeUrl`	No
`ownerPubkey`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Jul 31, 2026

TDQS

B3.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose meaningful traits: history is kept, the operation force-updates gittr branches to match the URL, and a 403 must not be retried or worked around. It stops short of stating auth/permission requirements beyond a passing "owner key" mention.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose is a plus, but the body is a run-on chain of clauses and the final sentence ("Leaving a dead forge is the website sidebar If this git host is gone, not this tool") is malformed and nonsensical, dragging down clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a write tool with no annotations, no output schema, and 0% parameter coverage, the behavioral cautions partially compensate. However, without any parameter explanation or auth detail, an agent lacks enough to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the description only loosely gestures at cloneUrl ("Git URL") and ownerPubkey ("owner key"). It says nothing about repo or bridgeUrl, so half the parameters remain undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ("Copy a Git URL onto the bridge") and immediately distinguishes itself from siblings mirrorRepo and pushToBridge. The core purpose is clear, though the trailing garbled sentence muddies the finish.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use mirrorRepo to also publish the Nostr card, do not use pushToBridge to sync a forge, and read with bridgeListFiles. It covers when-not and alternatives well, but the final sentence about a dead forge is incoherent enough to weaken the guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server