Skip to main content
Glama
Sign In
muhammad-awais-web-dev

portfolio-mcp-server

by muhammad-awais-web-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to portfolio-mcp-server

No user-submitted related servers found.

    Related Servers

    • Portfolio MCP Server

      Yunwcy
      A
      license
      A
      quality
      B
      maintenance
      Exposes a personal portfolio of projects, skills, and resume as callable tools for MCP-compatible AI assistants like Claude Desktop.
      4
      MIT

    • daksh-mcp

      mrcodefrost
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible AI clients to retrieve a professional profile as callable tools, including projects, work experience, skills, and live GitHub activity.
      5
      MIT

    • Duly

      Rashed-Almasri5505
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents to access privacy-redacted document reading, deadline tracking, memory, drafting, and privacy-checked model and web-search tools over stdio.
      MIT

    • kazejev-personal

      theglobe
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to retrieve a personal biography, skills, projects, and contact links through a read-only MCP server.
      -
    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

    B3.3/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear list/get/create/update/delete separation. There is no meaningful overlap or ambiguity between any of the 32 tools.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout: list_ for collections, get_ for single items, and create_/update_/delete_ for mutations. This makes the API surface highly predictable.

    Tool Count2/5

    With 32 tools, the server is over-scoped for a portfolio use case, exceeding the threshold where tool selection becomes a cognitive burden. While the CRUD pattern is systematic, most real portfolio workflows would only need a small subset of read operations.

    Completeness5/5

    The tool set provides complete CRUD coverage for every portfolio content type, plus profile management. There are no obvious dead ends or missing lifecycle operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources