Runnable example of node-candidate-mcp-server.
Runnable example of node-candidate-mcp-server. That is what the http server with mcp support mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
An HTTP server built with Express and TypeScript that serves both a webpage and a Model Context Protocol (MCP) endpoint.
The server publishes 8 tools. What each one is for:
CONTACT_EMAIL — The contact email address for the serverMAILGUN_API_KEY — The API key for Mailgun, used for sending emailsMAILGUN_DOMAIN — The domain for Mailgun, used for sending emailsCANDIDATE_NAME — The name of the candidateRESUME_URL — The URL to the candidate's resume in PDF formatLINKEDIN_URL — The URL to the candidate's LinkedIn profileGITHUB_URL — The URL to the candidate's GitHub profileWEBSITE_URL — The URL to the candidate's personal websiteConfiguration is passed through the environment: MAILGUN_API_KEY, RESUME_URL, LINKEDIN_URL, GITHUB_URL, WEBSITE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. HTTP Server With MCP Support's toolset — CONTACT_EMAIL, MAILGUN_API_KEY, MAILGUN_DOMAIN and 5 more — is a fair guide to whether it matches your workflow. It is maintained by jhgaylor; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against HTTP Server With MCP Support's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| CONTACT_EMAIL | The contact email address for the server. |
| MAILGUN_API_KEY | The API key for Mailgun, used for sending emails. |
| MAILGUN_DOMAIN | The domain for Mailgun, used for sending emails. |
| CANDIDATE_NAME | The name of the candidate. |
| RESUME_URL | The URL to the candidate's resume in PDF format. |
| LINKEDIN_URL | The URL to the candidate's LinkedIn profile. |
| GITHUB_URL | The URL to the candidate's GitHub profile. |
| WEBSITE_URL | The URL to the candidate's personal website. |
| Variable | Description | Required |
|---|---|---|
| MAILGUN_API_KEY | Credential the server authenticates with. | Yes |
| RESUME_URL | Endpoint or connection string the server talks to. | Yes |
| LINKEDIN_URL | Endpoint or connection string the server talks to. | Yes |
| GITHUB_URL | Endpoint or connection string the server talks to. | Yes |
| WEBSITE_URL | Endpoint or connection string the server talks to. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.