Skip to main content
Glama

Related Servers

Alternatives to Basecamp MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Enables seamless integration with Basecamp 3 through 46 comprehensive API tools, allowing users to manage projects, todos, card tables, documents, campfire messages, and other Basecamp features through natural language interactions in Claude Desktop and Cursor IDE.
      33
      5
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable clients such as Codex, Cursor, and Claude Desktop to read and manage Basecamp 3 projects through OAuth-authenticated API calls, covering projects, todos, messages, card tables, documents, uploads, and search. It exposes these capabilities as tools for browsing, creating, updating, and organizing Basecamp content via natural language.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Connects AI assistants to the Basecamp 2 API, enabling management of projects, todos, messages, and people directly through natural language.
      17
      10 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable clients such as Codex, Cursor, and Claude Desktop to read and manage Basecamp 3 projects through OAuth-authenticated API calls. Covers projects, todolists and todos, message boards, campfires, card tables, inbox forwards, documents, uploads, comments, events, webhooks, and search.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable clients like Codex, Cursor, and Claude Desktop to read and manage Basecamp 3 projects through OAuth-authenticated API calls. Exposes tools for projects, todos, message boards, card tables, documents, uploads, comments, webhooks, and search.
      -

    TDQS

    A3.7/5.0

    Scored across 57 tools

    Disambiguation4/5

    Each tool targets a distinct resource+action, and the descriptions explicitly differentiate overlapping cases (e.g. list_recordings vs per-project list tools, move_todo vs reorder_todos, complete_todo vs uncomplete_todo). A few conceptual overlaps remain (get_upload vs download_blob, list_documents vs list_recordings), but they are clearly scoped.

    Naming Consistency5/5

    Every tool follows the same basecamp_verb_noun convention (basecamp_create_message, basecamp_update_todo, basecamp_list_projects, basecamp_move_kanban_card, basecamp_trash, basecamp_restore). Verbs and resource nouns are used predictably throughout, with no mixing of conventions.

    Tool Count3/5

    57 tools is well beyond the typical 3-15 sweet spot and is heavy even for a broad domain like Basecamp. To their credit the tools are not redundant and each covers a real resource/operation, but the surface is large enough to strain discovery.

    Completeness5/5

    Coverage spans the full Basecamp domain: projects, people, messages, todos/todolists/groups, vaults, documents, uploads, kanban, check-ins (questionnaires/questions/answers), campfire, recordings, comments, attachments, plus auth. CRUD is complete for each area, with trash/restore handling deletion and dedicated tools for ordering and moving items.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data