daksh-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional GitHub token to raise API rate limits from 60/hr (unauthenticated) to 5000/hr. The server works without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_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. |
| list_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. |
| get_experienceA | Returns Daksh's work history: company, title, dates, summary, and achievements. Optionally filter to a single company. |
| get_skillsA | Returns Daksh's skills grouped by category (languages, backend, cloud, ai-tooling, etc). Optionally filter to one category. |
| get_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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
Five tools is well-scoped for a personal professional profile server. Each tool serves a clear purpose without redundancy or bloat.
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.