Priya Gautam MCP Server
Related Servers
Alternatives to Priya Gautam MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAggregates your digital footprint (GitHub, blogs, resume) into a single AI-readable profile and exposes it via MCP tools so AI agents can query your context live.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to discover and retrieve professional portfolio information including profile, experience, skills, projects, and contact details through MCP tools.-
- FlicenseAqualityBmaintenanceEnables MCP-compatible AI clients to retrieve a professional profile as callable tools, including projects, work experience, skills, and live GitHub activity.5-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides unified access to one's professional profile, including experience, publications, career timeline, and social media presence.1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceExposes a person's structured professional profile as MCP tools, enabling Claude and other MCP clients to answer questions about that person based on real data.3 npm1MIT

antlis-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables AI assistants to query a developer's portfolio, including projects, experience, and technical background, through structured MCP tools.-
TDQS
Scored across 9 tools
There is significant overlap: get-profile, get-skills, get-projects, get-education, and get-experience provide section-specific data, but search-priya-profile and search-profile are near-duplicates both using DCR to search the entire profile. Agents could easily misselect between search-priya-profile and search-profile, and between the individual getters and search tools when a broad query comes in.
Most tools follow a clear get-<section> pattern (get-profile, get-skills, get-projects, get-education, get-experience) and list-sections, but search-priya-profile breaks the pattern by embedding the person's name instead of using a consistent 'search-<target>' prefix like search-profile does. The inconsistency between the two search tool names is the main deviation.
9 tools is a reasonable count for a profile server, but the surface feels padded: search-priya-profile and search-profile appear to be redundant duplicates serving the same purpose, and explain-dcr is more documentation than a functional tool. The effective distinct tool count is closer to 6-7.
The server covers profile sections well (skills, projects, education, experience, plus a compact overview). Minor gaps exist, such as no dedicated tools for certifications or achievements despite those being mentioned in search descriptions, but the search tool can still surface that data.