Skip to main content
Glama
x51xxx

OSP Marketing Tools MCP Server

by x51xxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to OSP Marketing Tools MCP Server

No user-submitted related servers found.

    Related Servers

    • WithSeismic MCP

      dougwithseismic
      A
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript implementation of a Model Context Protocol server that provides a frictionless framework for developers to build and deploy AI tools and prompts, focusing on developer experience with zero boilerplate and automatic tool registration.
      681 npm
      14
      MIT

    • MCP Server TypeScript

      YanViniciusSilva
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server implemented in TypeScript that provides resources, tools (calculator, weather, timestamp), and prompts for integration with LLMs.
      205 npm
      ISC

    • @zhama/mcp-server

      zhama-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript framework for building Model Context Protocol servers with a decorator-based API, enabling custom tools, resources, and prompts for AI applications.
      22 npm
      MIT

    • MCP Server Template

      stevennevins
      A
      license
      C
      quality
      D
      maintenance
      A TypeScript-based template for developing Model Context Protocol servers with features like dependency injection and service-based architecture, facilitating the creation and integration of custom data processing tools.
      1
      6 npm
      4
      ISC
    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

    B3.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: editing codes, meta guide, SEO guide, value map positioning, writing guide, and health check. The descriptions specify unique domains (e.g., semantic editing marks vs. web content optimization), making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'get_' prefix for five tools and a descriptive 'health_check' for the sixth. The naming is uniform and predictable, using snake_case throughout without deviations.

    Tool Count4/5

    Six tools are reasonable for a marketing-focused server, covering key areas like SEO, content creation, and positioning. It's slightly thin but well-scoped; each tool earns its place without redundancy or obvious gaps in the core domain.

    Completeness3/5

    The tools provide comprehensive guides for content creation, SEO, and positioning, but they are all 'get' operations with no create/update/delete actions. This limits agent workflows to retrieval only, leaving notable gaps for interactive or generative tasks in the marketing domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources