Skip to main content
Glama
daksh-mcp

daksh-mcp

by mrcodefrost

daksh-mcp

An MCP (Model Context Protocol) server that exposes a professional profile — projects, work experience, skills, and live GitHub activity — as tools any MCP-compatible AI client (Claude Desktop, Claude Code, etc.) can call.

Connect it to Claude Desktop and ask things like "What fintech projects has this person shipped?" or "Summarize their experience at [company]" — the client calls these tools and answers from real, structured data instead of a resume PDF.

Tools exposed

Tool

Input

What it does

get_profile

(none)

Name, title, summary, location, contact/social links

list_projects

tag?, limit?

Projects, optionally filtered by tag (e.g. "fintech")

get_experience

company?

Work history, optionally filtered by company

get_skills

category?

Skills grouped by category (languages, backend, cloud, ...)

get_github_activity

username?, limit?

Live call to the GitHub REST API for recently updated public repos

All inputs are validated with Zod schemas.

Related MCP server: personal-context

Project structure

data/profile.json       Static source data — replace this with your own info
src/schema.ts           Zod schemas for the profile data shape
src/data.ts             Loads + validates profile.json at startup
src/github.ts           GitHub REST API client (fetch-based, optional token)
src/tools/*.ts          One file per tool: input schema + handler
src/index.ts            Wires everything into an McpServer over stdio

Setup

npm install
cp .env.example .env   # optional: add a GITHUB_TOKEN to raise API rate limits
npm run build

Then edit data/profile.json with your own projects, experience, and skills.

Running & testing locally

Option A — MCP Inspector

npm run build
npx @modelcontextprotocol/inspector node dist/index.js

Opens a browser UI to see the tool list and call each tool with arbitrary arguments.

Option B — Claude Desktop

Add this server to Claude Desktop's config file:

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "daksh-mcp": {
      "command": "node",
      "args": ["ABSOLUTE_PATH_TO_REPO/dist/index.js"]
    }
  }
}

Restart Claude Desktop and ask it questions about the profile in data/profile.json.

Option C — Claude Code

Claude Code can attach to the same server via claude mcp add, using the same command/args as above.

Environment variables

See .env.example. GITHUB_TOKEN is optional — it raises the GitHub API rate limit from 60/hr (unauthenticated) to 5000/hr. The server works without it.

Available Tools

5 tools
get_experienceGet ExperienceA

Returns Daksh's work history: company, title, dates, summary, and achievements. Optionally filter to a single company.

Inputs: company.

get_github_activityGet GitHub ActivityA

Fetches a live list of recently updated public repositories for a GitHub user via the GitHub REST API (bonus tool demonstrating a real external API integration, not static profile data). Defaults to Daksh's own GitHub username.

Inputs: limit, username.

get_profileGet ProfileA

Returns Daksh's professional identity: name, title, summary, location, and contact/social links. Use this first for any 'who is this person' style question.

Inputs: no named parameters.

get_skillsGet SkillsA

Returns Daksh's skills grouped by category (languages, backend, cloud, ai-tooling, etc). Optionally filter to one category.

Inputs: category.

list_projectsList ProjectsA

Lists Daksh's projects, optionally filtered by tag (e.g. 'fintech') and capped by limit. Each project includes description, role, tech stack, highlights, and links.

Inputs: tag, limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct facet of Daksh's professional identity: profile, projects, experience, skills, and GitHub activity. There is no meaningful overlap between the tools, and the descriptions reinforce their unique purposes.

    Naming Consistency4/5

    The naming pattern is mostly consistent with get_* for singular resources (get_profile, get_experience, get_skills, get_github_activity). The one deviation is list_projects, which uses list_ instead of get_, but it remains clear and predictable.

    Tool Count5/5

    Five tools is well-scoped for a personal professional profile server. Each tool serves a clear purpose without redundancy or bloat.

    Completeness5/5

    The tool set covers the core sections of a professional identity: bio, projects, work history, skills, and live GitHub activity. Contact and social links are included in the profile, so there are no obvious missing operations for the server's stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes 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.
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Aggregates 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.
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Exposes a personal portfolio of projects, skills, and resume as callable tools for MCP-compatible AI assistants like Claude Desktop.
      4
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to retrieve a personal biography, skills, projects, and contact links through a read-only MCP server.
      -