Skip to main content
Glama
r28ai

Marketing Ops

by r28ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Marketing Ops

No user-submitted related servers found.

    Related Servers

    • Chief of Staff

      r28ai
      A
      license
      B
      quality
      B
      maintenance
      Runs 20 slash-command workflows across Google Calendar, Gmail, Linear, Slack, Granola, Google Docs, GitHub, Stripe, Notion, Google Forms, Sheets and Drive to produce morning briefs, meeting prep, action items assigned to owners and weekly updates. Reads proceed without asking, while anything that creates, sends, changes or deletes is shown for approval first.
      47
      Apache 2.0

    • Product Manager MCP

      r28ai
      A
      license
      B
      quality
      B
      maintenance
      Enables an agent to run 20 product-management workflows that convert call notes, specs, customer feedback and competitor changes into deduped Linear issues, PRD drafts, roadmap sheets, digests and weekly project updates. Orchestrates only the tools each workflow needs across Granola, Linear, Slack, Notion, GitHub, Stripe, Firecrawl, Tavily and Google Workspace, using credentials kept in the user's own OS keychain.
      51
      Apache 2.0

    • Web Research to Docs

      r28ai
      A
      license
      B
      quality
      B
      maintenance
      Enables an agent to run ten ready-made research and monitoring workflows — competitor digests, cited reports, paper alerts, market maps, regulatory and due-diligence watches — pulling from Firecrawl, Tavily, GitHub and landing results in Notion, Slack, Google Docs, Sheets and Linear. Fields are filed with the user's own keys held in the operating system keychain, and every action that creates, sends or changes anything is shown and approved first.
      21
      Apache 2.0

    • Shopify Store Ops

      r28ai
      A
      license
      B
      quality
      B
      maintenance
      Runs twelve agent workflows over Shopify, Google Sheets, Gmail, Slack, Firecrawl, Linear and Stripe — drafting supplier reorders, answering order-status emails, posting daily sales digests, importing supplier catalogues into the store, handling cancellations and wholesale orders, flagging fulfillment exceptions, and consolidating revenue from multiple payment sources. Each workflow is a slash-command prompt backed by only the tools it needs, with reads running freely and any write shown for approval first.
      28
      Apache 2.0

    • Freelancer Ops MCP

      r28ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables freelancers and agencies to run eight back-office workflows across Stripe, Google Drive, Linear, Google Calendar, Gmail, GitHub, Google Docs, Granola, Google Sheets and Firecrawl, covering client onboarding, invoices from calendar and commits, status reports, scope-creep detection, site audits and overdue invoice chasers. Reads run freely, while anything that creates, sends, changes or deletes is shown for approval first, with credentials kept in your own OS keychain and no proxying through any third-party server.
      Apache 2.0

    • GitHub + Linear Dev Workflows

      r28ai
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that turns CI failures, pull requests, security alerts, and Slack threads into Linear issues, Slack posts, changelogs, docs, and reports with evidence attached, through 25 agent-run workflows over 59 tools spanning GitHub, Linear, Slack, Notion, Google Docs, Google Calendar, Google Sheets, Firecrawl, and Tavily. It also handles credential setup in the OS keychain and pauses for approval before any create, send, change, or delete call.
      Apache 2.0
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 29 tools

    Disambiguation4/5

    Tools are namespaced by app (linear_, github_, firecrawl_, etc.) with a distinct resource+action per tool, so cross-app confusion is minimal. The only mild overlap is within firecrawl (scrape's 'optional structured extraction' vs extract) and the meta pair connect/connection_status, but descriptions differentiate them clearly.

    Naming Consistency4/5

    The dominant pattern is consistent app_resource_action with the verb last (linear_issues_list, gmail_messages_send, stripe_customers_list). Deviations are minor: inconsistent pluralization (linear_issues_list vs linear_issue_create) and the two meta tools (connect, connection_status) that abandon the pattern entirely.

    Tool Count3/5

    At 29 tools this is on the heavy side of the rubric, though the breadth is explained by spanning 13+ distinct apps, each contributing only 1-3 tools. It feels borderline: justified by multi-app scope but still a large surface an agent must navigate.

    Completeness2/5

    Coverage is a thin slice per app and several descriptions point to tools that do not exist in this set: linear_issue_create references teams_list/users_list/workflow_states_list, gdocs_documents_create references documents_batch_update, gforms_forms_create references forms_batch_update, and granola_notes_list references notes_get. These dangling references create dead ends that will cause agent failures.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources