Skip to main content
Glama
wyattjoh
by wyattjoh

Related Servers

Alternatives to @wyattjoh/forgejo-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to read a Forgejo, Codeberg, or Gitea instance—including users, repositories, issues, pull requests, search, notifications, comments, reviews, and Actions runs—with opt-in, time-boxed guarded writes for repository, branch, issue, pull request, comment, migration, push-mirror, and workflow operations.
      59
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables users to manage self-hosted Git repositories from ChatGPT and compatible Codex clients via OAuth-secured connections, with independent browser approval for write actions. Supports repository, file, branch, issue, pull request, release, and workflow operations while excluding administrative tools.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables clients to discover and read authorized vessel telemetry, state snapshots, and historical data, and to inspect and invoke approved read-only core or plugin operations over Streamable HTTP. It reuses the existing Signal K bearer tokens, permissions, and staleness/ACL checks, requiring no extra account, key, listener, or container.
      559 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a hosted remote connection to Mobbin's library of real-world app and web design references over Streamable HTTP, requiring nothing to install or run locally. Access is authorized through an OAuth browser sign-in on first use, with per-client setup and tool listings documented externally.
      65
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to connect once to self-hosted, user-owned upstream accounts and then discover and invoke granted tools through a single authenticated endpoint. Each client receives its own key with deny-by-default tool grants, while sensitive calls require durable human approval and credentials stay encrypted and never forwarded upstream.
      Apache 2.0