Developer Tools

gitback.us

An MCP server for inspecting GitHub-backed public boards and retrieving their feedback, roadmap, changelog, FAQ, and issue data.

1 endpoint20 known toolsFirst detected October 18, 2026Last detected October 18, 2026

ENDPOINT 1

https://gitback.us/api/mcp

No auth detected

MCP server metadata

Name: gitback
Version: 0.1.0

Capabilities

tools.listChangedresources.listChanged

Server instructions

Gitback serves a Board for a public GitHub repo: its feedback, roadmap, changelog, FAQ and issues, read live from that repo. Glossary: A Board is the one page Gitback serves for one public GitHub repo, named by `owner/repo`. A Module is one of a Board's five fixed sections: Feedback, Roadmap, Changelog, FAQ and Issues. A Client is the GitHub account with write access to the repo that has claimed its Board. An End User is anyone who signs in with GitHub to post feedback or Vote on a Board they do not own. A Vote is a 👍 reaction on a feedback item or roadmap Issue by a real GitHub account, never GitHub's own Discussion upvote. The Category Mapping is which of the repo's Discussion categories a Board uses for feedback and for questions. Every tool takes `repo` as `owner/repo`; call `board.get` first to learn whether the repo is a Board and which Modules have content. Reads are anonymous, writes need sign-in, and the four deep-link tools (`feedback.draft`, `feedback.vote`, `roadmap.setStatus`, `changelog.markShipped`) remain the path for hosts without inline forms.

Known tools 20

board.get

Whether a public GitHub repo is a Gitback Board, and what it holds: whether a Client has claimed it, each Module it shows visitors (of Feedback, Roadmap, Changelog, FAQ, Issues) with a count and its newest item, the Category Mapping (which Discussion categories hold feedback and questions, by name), its Custom Domain if one is bound, and whether the repo footprint consent is granted, declined or unasked.

Inferred read-only

feedback.list

The Feedback Module of a Board: its feedback items (GitHub Discussions in the mapped category), each with its Votes (👍 reactions by real GitHub accounts), kind, state, author, last-updated day and github.com url.

Inferred read-only

feedback.get

One feedback item from a Board's Feedback Module, by number: the full body, its Votes, the author, and its comments with their authors and dates, plus its github.com url.

Inferred read-only

roadmap.list

The Roadmap Module of a Board: its GitHub Issues by lane (open, planned, in-progress, complete), each with its Votes (👍 reactions), labels, last update and github.com url.

Potential side effects

changelog.list

The Changelog Module of a Board: its GitHub Releases, newest first, each with the roadmap items it closed and their Votes — the join GitHub's own release list does not have.

Inferred read-only

faq.search

Search the FAQ Module of a Board: the entries whose question or answer contains `query` (case-insensitive), each with its full answer, tags and github.com url.

Inferred read-only

issues.get

One open GitHub Issue from a Board's Issues Module, by number: its title, state, opener, comment count, labels, opening day, the roadmap items it is linked to, and its github.com url.

Inferred read-only

insights.demand

The Board's open feedback items with the most Votes, most first — what End Users want most.

Inferred read-only

insights.stale

The Board's open feedback items nobody has updated in more than `days` days, stalest first, with how many there are in all.

Inferred read-only

insights.loop

Roadmap items in the complete lane that no Release cites, and Releases that cite no roadmap item — the shipped work nobody has told the askers about.

Inferred read-only

insights.velocity

Per ISO week, newest first: new feedback items and their Votes, new roadmap items, and Releases published.

Inferred read-only

feedback.draft

Drafts a new feedback item for a Board's Feedback Module and returns a link a human opens to review and post it themselves, with up to five existing items it resembles (number, title, Votes, url) so they can Vote for one instead of posting a duplicate.

Potential side effects

feedback.vote

Returns a link that opens one feedback item on a Board with its Vote control ready, for a human to Vote themselves (a 👍 reaction under their own GitHub account).

Inferred read-only

roadmap.setStatus

Returns a link that opens a roadmap item's move control on a Board with the target lane (open, planned, in-progress, complete) selected, for the Board's Client to confirm.

Inferred read-only

changelog.markShipped

Composes the comment that tells the people who asked for roadmap items that a Release shipped them — each item with its Votes — and returns it with a link the Board's Client opens to review and post it on each item's thread.

Potential side effects

feedback.submit

Posts a new feedback item to a Board's Feedback Module as a GitHub Discussion authored by the signed-in caller, and returns its url.

Inferred read-only

feedback.castVote

Casts the signed-in caller's Vote (a 👍 reaction under their own GitHub account) on one feedback item.

Inferred read-only

roadmap.applyStatus

Moves a roadmap item to a lane (open, planned, in-progress, complete) by swapping its labels on GitHub, as the signed-in caller.

Inferred read-only

changelog.postLoopComment

Posts the given comment, as the signed-in caller, on each roadmap item a Release shipped, telling the people who asked for it.

Inferred read-only

whoami

The GitHub login the app-only write tools act as on this connection, or null when it is not signed in to Gitback.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.gitback]
url = "https://gitback.us/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "gitback": {
      "type": "http",
      "url": "https://gitback.us/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: gitback
Remote MCP URL: https://gitback.us/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "gitback": {
      "url": "https://gitback.us/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "gitback": {
      "type": "http",
      "url": "https://gitback.us/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "gitback",
  "transport": "streamable-http",
  "url": "https://gitback.us/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.