Skip to main content
Glama
Sign In
agente-local

agente-local

by felipebherve
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agente-local

No user-submitted related servers found.

    Related Servers

    • Ollama MCP Server

      Jadael
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude to delegate coding tasks to local Ollama models, reducing API token usage by up to 98.75% while leveraging local compute resources. Supports code generation, review, refactoring, and file analysis with Claude providing oversight and quality assurance.
      464 npm
      26
      AGPL 3.0

    • claude-token-saver-mcp

      BlackFoil
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to offload routine code generation and text processing tasks to a local Ollama LLM, saving Cloud API tokens and costs with automatic model selection and security features.
      11
      281 npm
      3
      Apache 2.0

    • ollama-agent

      Shaing
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Code to leverage local Ollama models for tasks like summarizing large files, reviewing diffs, semantic code search, and generating boilerplate or tests, while also supporting a fully offline mode.
      6
      MIT

    • io.github.bdbais/routeai

      bdbais
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code to offload small coding tasks to local Ollama machines and free or paid AI providers, choosing the cheapest available option while enforcing quotas, budgets, and Claude's final review.
      11
      MIT
    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

    B3.1/5.0

    Scored across 37 tools

    Disambiguation3/5

    Most tools have clearly distinct scopes (git_*, navegador_*, janela_*, índice de projeto), but three tools—pergunta_local, segunda_opiniao and pedir_ao_agente—all delegate to local models with overlapping intent, and three separate click tools (navegador_clicar, janela_clicar, tela_clicar) force the agent to infer which layer a button belongs to. The descriptions do help disambiguate, but an agent must read carefully before choosing. A single Maestro router plus two direct LLM tools is redundant surface.

    Naming Consistency3/5

    Most names follow a readable Portuguese resource_action pattern (navegador_abrir, janela_ler, git_status, tela_clicar, contexto_projeto), but this is mixed with verb_noun forms (abrir_pr, abrir_app, ler_relevante, indexar_projeto, resumir_texto) and bare verbs/nouns (lembrar, falar, segunda_opiniao, relatorio_economia, status_agente, braco_liberar). All snake_case and legible, but no single predictable convention.

    Tool Count2/5

    37 tools is well above the practical ceiling for a single MCP server and requires the agent to scan a long catalog before every action. The breadth (browser, desktop windows, vision, git, project indexing, local LLM, TTS, file organizing) is real but would be better split into domain-specific servers or namespaced groups.

    Completeness4/5

    Coverage is impressively broad for a local PC agent: browser and window control, git lifecycle (status/pull/branch/commit/merge/push/PR), project indexing and memory, testing, review, and local-model delegation are all present. The main gap is file writing/editing—there are readers and summarizers (ler_relevante, resumir_arquivo) but no clear tool to create or modify a file's content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources