Skip to main content
Glama
vapvarun

Basecamp MCP Server

by vapvarun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Basecamp MCP Server

No user-submitted related servers found.

    Related Servers

    • Basecamp MCP Server

      Felix2171
      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.
      -

    • Basecamp MCP Server

      jacob1660
      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 and related resources through OAuth-authenticated API calls, with tools for todos, messages, card tables, documents, uploads, comments, events, webhooks, and search.
      -

    • Basecamp MCP Server

      elifpatel
      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.
      -
    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

    C2.5/5.0

    Scored across 88 tools

    Disambiguation2/5

    Several tools have overlapping purposes, such as basecamp_read vs. basecamp_get_card/basecamp_get_todo, basecamp_comment vs. basecamp_comment_with_file, and basecamp_trash_recording vs. basecamp_trash_card/basecamp_trash_project. Agents may struggle to choose the correct tool without deep domain knowledge.

    Naming Consistency4/5

    Most tools follow the predictable pattern basecamp_<verb>_<noun> (e.g., list_projects, create_card, update_todo). Minor deviations include basecamp_comment, basecamp_read, basecamp_comment_with_file, and the index_* group, which uses a slightly different prefix style.

    Tool Count1/5

    With 88 tools, the server is extremely bloated. Many tools are redundant or overly granular (e.g., list_cards vs. list_card_ids, multiple index helpers). The count far exceeds what is needed for a coherent MCP server, likely overwhelming agents.

    Completeness4/5

    The tool surface covers almost all major Basecamp resources: projects, card tables, todos, messages, vaults, documents, uploads, schedule, campfires, and people. Minor gaps exist, such as no direct campfire line update or message deletion, but generic trash/archive/activate tools partially fill these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources