Skip to main content
Glama
Sign In
aplaceforallmystuff

MCP Pickaxe Server

by aplaceforallmystuff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP Pickaxe Server

No user-submitted related servers found.

    Related Servers

    • Forge MCP Server by SalesforgeAI

      Forge MCP Serverofficial

      SalesforgeAI
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to the complete Salesforge product suite, enabling management of workspaces, contacts, sequences, mailboxes, domains, and more across multiple sales tools.
      68 npm
      2
      MIT

    • WorkForceAI MCP Server

      shandanawerkx
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to look up and update WorkForceAI platform data, including voice agents, campaigns, phone numbers, call logs, and dashboard stats, through natural language.
      -

    • Purl MCP Server

      ykovenskiy-hub
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to live Purl Studio projects, enabling reading objects, modifying scripts, and setting properties.
      26
      5 npm
      MIT

    • DocsMint MCP Server

      ricci8219
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents access to a persistent document workspace, letting them search, read, and update notes, guides, and project documentation across a full catalog of tools, prompts, and resources. It connects either to the hosted Cloud endpoint over Streamable HTTP with OAuth or API-key auth, or to a self-hosted instance through a stdio bridge.
      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

    A3.6/5.0

    Scored across 17 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. Tools are organized by resource types (documents, users, memories, products, studios, chat history) and specific actions (create, get, list, update, delete, connect/disconnect), making it easy for an agent to select the correct tool without confusion.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as doc_create, user_list, memory_get_user, and studios_list. All tools use snake_case with clear, descriptive names, providing a predictable and readable structure across the entire set.

    Tool Count5/5

    With 17 tools, the count is well-scoped for managing a Pickaxe studio's resources. Each tool earns its place by covering essential operations like CRUD for documents and users, plus additional functions for linking, memory, and studio management, without being excessive or insufficient for the domain.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for the Pickaxe domain, including documents, users, memories, products, studios, and chat history. There are no obvious gaps; agents can perform all necessary operations from creation to deletion, with additional utilities like connecting documents and inviting users, ensuring no dead ends in workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources