INDIVIDUAL MCP TOOL

whoami

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

gitback.usnone authenticationAvailability not checked

LIVE ENDPOINT

https://gitback.us/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for whoami and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.

Parent server

gitback.us

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.

Related tools

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.
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.
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.
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.
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.
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.
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.
insights.demand — The Board's open feedback items with the most Votes, most first — what End Users want most.