fenbs-mcp
OfficialRelated Servers
Alternatives to fenbs-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityAmaintenanceEnables local MCP clients to access the hosted Asyntai MCP server by bridging stdio to HTTPS and handling OAuth sign-in, giving assistants the same 52 tools as the Asyntai dashboard.5444 npm1MIT- AlicenseNot gradedqualityAmaintenanceBridge that lets stdio-only MCP clients connect to remote MCP servers with OAuth and other auth support, enabling local clients to use remote, authorized MCP servers.53 npm54MIT
- FlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, and Grok to a local machine through a single OAuth-gated MCP endpoint so they can browse, read, write, and edit files, run whitelisted shell commands, search content, use Git, query SQLite, drive browsers and DevTools, and manage background tasks, ports, and clipboard. It also exposes localhost and LAN services via a protected HTTP client, letting remote or mobile clients debug and operate local projects without granting unrestricted shell access.-
- AlicenseNot gradedqualityAmaintenanceConnects web-based AI chat clients such as Claude, ChatGPT, Grok, and Postman to a local machine through a single OAuth-gated MCP endpoint, so they can build and edit projects, run whitelisted shell commands, search files, inspect databases and local APIs, drive browsers and DevTools, manage background jobs, and control Postman without granting unrestricted shell access. It also supports local IDEs and offline use by connecting directly over localhost.MIT

sombra-mcpofficial
AlicenseNot gradedqualityDmaintenanceA stdio-to-HTTP bridge for connecting to Sombra's remote MCP server, enabling AI agents to save, search, and organize web content.8 npmMIT- AlicenseNot gradedqualityCmaintenanceA lightweight stdio-to-http relay that enables the GitHub MCP server to authenticate using a GitHub App instead of a Personal Access Token. It automatically manages fine-grained permissions and short-lived tokens for secure, organizational AI agent workflows.MIT
TDQS
Scored across 30 tools
Most tools have clearly distinct purposes, with detailed descriptions distinguishing decisions, context notes, tasks/items, projects, flags, and approvals. Minor ambiguity remains because the same task resource is called 'item' in tool names but 'task' in other tools, and rules can be read via both fenbs_get_context and fenbs_list_decisions.
All tools use a consistent fenbs_ prefix and snake_case, and most follow a verb_noun pattern such as fenbs_list_items or fenbs_update_decision. The main deviation is terminology: task-oriented tools use 'task' while the core CRUD tools use 'item', plus fenbs_whoami, fenbs_comment, and fenbs_search break the verb_noun pattern slightly.
With 30 tools, the surface is heavy for the apparent scope, exceeding the threshold where each tool clearly earns its place. Many delete/restore/update variants across items, decisions, context notes, and projects could be consolidated or better grouped.
The server covers CRUD and lifecycle operations well for tasks/items, decisions, context notes, and projects, including restore, flagging, commenting, sign-off requests, and pre-approved task flow. Minor gaps exist around board-level administration, file operations, and direct sign-off actions, but core agent workflows are supported.