Skip to main content
Glama
firasshaari

openwifi-mcp

by firasshaari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to openwifi-mcp

No user-submitted related servers found.

    Related Servers

    • CoolPlugz

      adaOctopus
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables autonomous Jira-to-PR workflows in Claude Code by fetching context from Jira, GitHub, Notion, and Slack, building structured prompts, and handling branch pushes, PR creation, CI polling, and task completion.
      1
      MIT

    • codex-mcp-server

      tuannvm
      A
      license
      A
      quality
      D
      maintenance
      Bridges Claude and OpenAI's Codex CLI for AI-powered code analysis, generation, and review, with support for session management, web search, and structured output.
      6
      1,265 npm
      647
      ISC

    • claude-opencode-mcp-v2

      choruzo
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to delegate software-engineering tasks to OpenCode agents running in the same workspace/worktree, with the model and provider chosen per agent. Exposes tools for task delegation, persistent sessions, diffs, and agent listing so an orchestrator can research, edit, review, and test code.
      7
      1,043 npm
      MIT

    • JIRA MCP Server

      CarloDeStefano90
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude Code to interact with JIRA through natural language, supporting issue creation, updates, searches, and workflow transitions, designed for enterprise intranets.
      22
      212 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a distinct and unambiguous purpose: help, status, start, tail, fetch, and deploy. No two tools overlap in functionality, ensuring an agent can easily select the correct one.

    Naming Consistency5/5

    All tools follow a consistent 'build_<verb>' pattern with imperative verbs (help, status, start, tail, fetch, deploy). This makes the tool surface predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the set is well-scoped for the domain of building and deploying OpenWiFi firmware. It covers the entire workflow without being excessively large or insufficient.

    Completeness4/5

    The tools cover the core lifecycle: help, start build, monitor progress (status, tail), fetch artifacts, and deploy. Minor omissions like a cancel or cleanup tool exist, but the essential path is complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources