my-mcp-server
This server lets AI assistants query Aniket Charjan's structured resume over MCP instead of guessing.
Profile & contact: get name, role, location, summary, links, contact details, and availability.
Experience & education: pull full work history with highlights and per-role stack, plus education history.
Projects: list all projects or get one by partial name match.
Skills: view skills grouped by category, or check a specific skill with supporting evidence.
Career metrics: fetch headline highlights like latency cuts and revenue lift.
Full resume: retrieve the entire resume as Markdown or structured JSON.
Free-text search: search across experience, projects, and skills with sourced citations.
Prompts: screen for a role against a job description, or draft recruiter outreach.
Resources: expose the resume as MCP resources (
resume://full,resume://profile,resume://all).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@my-mcp-server What did Aniket do at BrowserStack?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
my-mcp-server
An MCP server that exposes Aniket Charjan's resume as a queryable API for AI assistants. Add it to Claude Desktop, Cursor, or any MCP client and ask "What did Aniket do at BrowserStack?" or "Has he shipped anything with WebRTC?" — answered from structured, sourced data instead of guesswork.
Real output from the server — has_skill returns evidence rather than a yes/no,
and search_background cites the project or skill group each match came from.
It implements all three MCP primitives — Tools, Resources, and Prompts — so it works as a complete reference server, not just a tool dump.
Tools
Tool | Returns |
| Name, current role, location, summary, links |
| Full work history with highlights and per-role stack |
| All side projects |
| One project by name (partial match) |
| Skills grouped by category |
| Whether he has a skill + supporting evidence |
| Headline career metrics |
| Education history |
| Contact details and availability |
| The entire resume as one Markdown document |
| Free-text AND-search across experience, projects, skills |
Related MCP server: personal-resume-agent
Resources
URI | Content |
| The full resume as Markdown |
| Profile summary as JSON |
| All structured data as JSON |
Prompts
Prompt | Purpose |
| Score Aniket's fit for a role, citing evidence |
| Draft a tailored recruiter outreach message |
Use it
No install and no npm account needed — npm can run it straight from this repo:
npx -y github:jason-bourne-gg/my-mcp-serverThat clones the repo, builds it, and starts the server on stdio.
Or clone it yourself if you want to poke at the source:
git clone https://github.com/jason-bourne-gg/my-mcp-server.git
cd my-mcp-server
npm install && npm run buildClaude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config), using
the absolute path to the built file:
{
"mcpServers": {
"aniket": {
"command": "node",
"args": ["/absolute/path/to/my-mcp-server/dist/index.js"]
}
}
}Restart Claude Desktop, then ask: "Using the aniket tools, what's his experience with LLMs?"
Cursor
Add the same block to ~/.cursor/mcp.json (or Settings → MCP).
To skip the build step entirely, point the client at the repo instead:
{
"mcpServers": {
"aniket": {
"command": "npx",
"args": ["-y", "github:jason-bourne-gg/my-mcp-server"]
}
}
}Develop
npm install
npm run build # tsc → dist/
npm start # run the built server on stdioSmoke-test over stdio without a client:
printf '%s\n' \
'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \
'{"jsonrpc":"2.0","method":"notifications/initialized"}' \
'{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \
'{"jsonrpc":"2.0","id":3,"method":"resources/list","params":{}}' \
'{"jsonrpc":"2.0","id":4,"method":"prompts/list","params":{}}' \
| node dist/index.jsAll content lives in src/data.ts — edit there and rebuild.
How it works
A stdio MCP server built on
@modelcontextprotocol/sdk.
It registers the tools, resources, and prompts capabilities and handles the
corresponding list / call / read / get requests. search_background and
has_skill run over a flattened index of every experience highlight, project, and
skill, returning each hit with its source. Tool handling is wrapped so a single
bad request can never crash the server, and SIGINT/SIGTERM shut it down
cleanly.
License
MIT © Aniket Ravindra Charjan
Available Tools
11 toolsget_contactC
Contact details and availability.
Inputs: no named parameters.
get_educationB
Education history.
Inputs: no named parameters.
get_experienceA
Full work history — roles, companies, periods, highlights, and per-role stack.
Inputs: no named parameters.
get_highlightsB
Headline career metrics (years, latency cut, revenue lift, etc.).
Inputs: no named parameters.
get_profileB
Aniket's profile: name, current role, location, summary, and links.
Inputs: no named parameters.
get_projectA
Details for one project by name (partial, case-insensitive match).
Inputs: name (required).
get_projectsB
All of Aniket's personal/side projects.
Inputs: no named parameters.
get_resumeA
The entire resume as a single formatted Markdown document.
Inputs: no named parameters.
get_skillsA
Technical skills grouped by category.
Inputs: no named parameters.
has_skillA
Check whether Aniket has a given skill and return supporting evidence from his skills and experience.
Inputs: skill (required).
search_backgroundA
Free-text search across experience, projects, and skills. Answers questions like 'what did he do at BrowserStack?'.
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
Each tool targets a distinct piece of information about the individual, with clear boundaries between contact, education, experience, projects, skills, and search. No two tools overlap in purpose.
Most tools follow a consistent get_<noun> pattern, but has_skill and search_background deviate from this convention, introducing minor inconsistency.
With 11 tools, the server covers a wide range of personal and professional details without being excessive. Each tool serves a distinct informational need.
The set covers all major aspects of a personal profile: contact, education, experience, skills, projects, resume, and search. It provides comprehensive read access to the individual's background.
Maintenance
Related MCP Connectors
Resume builder with native MCP — create and edit resumes from your AI assistant.
Akshay Shetty's engineering portfolio and resume, queryable by AI. OAuth-secured.
Build, version and render resumes as PDFs from Claude or any MCP client.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides a structured API for AI agents to query a person's resume, including profile, projects, writing, and gated access to experience and skills.MIT
- AlicenseNot gradedqualityDmaintenanceExposes a personalized AI agent that reads your resume and provides intelligent responses about your professional background through a standardized MCP server interface with RAG capabilities.MIT
- FlicenseAqualityDmaintenanceExposes a personal portfolio's resume, projects, skills, certifications, and live GitHub repositories as tools for AI assistants to query via natural language.6-
- AlicenseNot gradedqualityDmaintenanceExposes a structured professional resume as a set of AI-queryable tools, enabling AI clients like Claude Desktop to query summary, experience, skills, projects, and tailor resumes to job descriptions.1MIT