example-candidate
MCP server from jhgaylor/example-candidate-mcp-server
claude mcp add --transport stdio jhgaylor-example-candidate-mcp-server node dist/index.js \ --env GITHUB_URL="The URL to the candidate's GitHub profile." \ --env RESUME_URL="The URL to the candidate's resume in PDF format." \ --env WEBSITE_URL="The URL to the candidate's personal website." \ --env LINKEDIN_URL="The URL to the candidate's LinkedIn profile." \ --env CONTACT_EMAIL="The contact email address for the server." \ --env CANDIDATE_NAME="The name of the candidate." \ --env MAILGUN_DOMAIN="The domain for Mailgun, used for sending emails." \ --env MAILGUN_API_KEY="The API key for Mailgun, used for sending emails."
How to use
This MCP server is an HTTP server built with Express and TypeScript that exposes both a web interface and a Model Context Protocol (MCP) endpoint. It runs in a stateless, streamable HTTP mode and supports two transports: a web-based HTTP interface and an MCP transport over HTTP. The server is designed to serve candidate data (name, resume, and social links) while also offering an MCP endpoint for programmatic access to the candidate model context. To use it, deploy the server in a Node.js environment and run both the web transport and the MCP transport as configured by the provided npm scripts. The MCP endpoint accepts standard MCP requests, enabling clients to query or stream candidate data, while the web port serves a landing page and any related UI assets. Customization is achieved via environment variables that populate fields such as the candidate name, contact details, and URLs to resume and social profiles.
How to install
Prerequisites:
- Node.js 18+ installed on your system
- npm or yarn for package management
Installation steps:
-
Clone the repository: git clone https://github.com/your-username/example-candidate-mcp-server.git cd example-candidate-mcp-server
-
Install dependencies: npm install
-
Build (if applicable) and run transports:
- Start the HTTP web transport: npm run start:web
- Start the MCP transport (stdio or MCP stream as configured): npm run start
Optional: set environment variables to customize candidate data before starting, for example:
- CONTACT_EMAIL=someone@example.com
- CANDIDATE_NAME="Jane Doe"
- RESUME_URL="https://example.com/resume.pdf"
You can also modify them directly in src/config.ts and rebuild as needed.
Additional notes
Environment variables control the candidate data served by the MCP endpoint. Restart the server after changes to take effect. Typical issues include missing environment variables, port conflicts, or mismatched Node.js versions. If you’re deploying in a container or platform, ensure the environment variables are correctly passed to the process and that both the web and MCP transports are listening on their expected ports. The README lists the recommended variables: CONTACT_EMAIL, MAILGUN_API_KEY, MAILGUN_DOMAIN, CANDIDATE_NAME, RESUME_URL, LINKEDIN_URL, GITHUB_URL, and WEBSITE_URL.
Related MCP Servers
iterm
A Model Context Protocol server that executes commands in the current iTerm session - useful for REPL and CLI assistance
mcp
Octopus Deploy Official MCP Server
furi
CLI & API for MCP management
editor
MCP Server for Phaser Editor
DoorDash
MCP server from JordanDalton/DoorDash-MCP-Server
mcp
MCP сервер для автоматического создания и развертывания приложений в Timeweb Cloud