Skip to main content
Glama
Jemade

Personal Workspace MCP Server

by Jemade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Personal Workspace MCP Server

No user-submitted related servers found.

    Related Servers

    • toolkit-mcp

      harshhh817
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to query a local SQLite database read-only, search and read files within a sandboxed directory, and get current weather and forecasts via Open-Meteo, all through natural language.
      MIT

    • task-manager

      ethereal-ctrl
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to manage tasks in a local SQLite database, with tools for creating, listing, updating, and deleting tasks.
      MIT

    • weather-mcp

      darshan0548
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to answer real-world weather questions using live Open-Meteo data, with tools for current conditions, umbrella reasoning, outdoor suitability, and city comparisons.
      MIT

    • mcp-sqlite-tools-plus

      MauricioPerera
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to interact with local SQLite databases with full CRUD, schema introspection, foreign key relations, generated columns, and multi-format import/export (CSV, JSON, XLSX) through natural language.
      26
      6 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: task CRUD is well-separated from history, database schema is distinct from query execution, and location search is distinct from weather forecast. No two tools could be easily confused.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern (get_task, create_task, list_tasks, update_task, archive_task, restore_task, query_database, search_locations). A few tools use noun_noun instead (task_history, database_schema, weather_forecast), which is a minor deviation.

    Tool Count5/5

    11 tools across three sub-domains (tasks, database, weather) is well-scoped; each tool has a clear, non-redundant role and the count is appropriate for the server's purpose.

    Completeness5/5

    Task lifecycle is fully covered (create, read, update, archive, restore, history), database access is complete for read-only queries (schema + SELECT), and weather covers both location search and forecasting.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources