HireMe MCP
The first portfolio AI agents can hire. Profile, products, pricing and briefs over MCP.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http hireme-mcp 'https://mcp.djaouad.tech/mcp'
{
"mcpServers": {
"hireme-mcp": {
"type": "http",
"url": "https://mcp.djaouad.tech/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
HireMe MCP
The first portfolio AI agents can hire. An open Model Context Protocol server that exposes Djaouad Frih's real profile, shipped products, fixed pricing and a project-brief intake — so Claude, Cursor, ChatGPT or any MCP client can vet the work and file a brief on your behalf.
Live: **https://mcp.djaouad.tech** · MCP endpoint: https://mcp.djaouad.tech/mcp
Tools
| Tool | Type | What it does |
|---|---|---|
get_profile | read | Identity, stack, live products, availability, contact links |
search_projects | read | Semantic-ish search over shipped projects (proof of experience) |
get_pricing | read | Fixed-price services in USD with ETAs |
get_next_slot | read | Availability status + direct booking link |
submit_project_brief | write | Files a project brief → persisted + emailed. Rate limited per IP |
The famous flows
- Founder delegate — "Claude, find me an AI engineer under $2k and send them my requirements" → their agent calls
get_pricing→search_projects→ files a brief. - Recruiter deep-dive — "Has he actually shipped RAG?" → grounded answers with demo links.
- Comparison shopper — pricing + timeline vs. an agency, plus next opening.
Structure
backend/ Express + @modelcontextprotocol/sdk (Streamable HTTP, stateless)
POST /mcp ← MCP clients
/api/tools/:id ← same handlers over REST (widget, mobile)
/api/briefs ← admin inbox (Bearer ADMIN_TOKEN)
/widget.js ← embeddable badge
frontend/ Next.js console (Netlify → mcp.djaouad.tech): connect configs,
live playground, scenarios
mobile/ Expo app: profile, tool runner, admin briefs inbox
Run locally
cd backend && npm i && npm run dev # :4343
cd frontend && npm i && npm run dev # set NEXT_PUBLIC_API_URL=http://localhost:4343
cd mobile && npm i && npm start # Expo Go
Copy backend/.env.example → .env. Without DATABASE_URL it runs in memory-only demo mode; without Gmail creds email notifications are skipped silently.
Deploy
- Backend → Render:
render.yamlincluded (free tier). SetDATABASE_URL,ADMIN_TOKEN, optionalGMAIL_USER/GMAIL_APP_PASSWORD. - Frontend → Netlify: repo import picks up
netlify.toml(static export). Attach custom domainmcp.djaouad.tech. - Mobile → APK:
eas build -p android --profile previeworexpo run:android.
Connect in one paste
{ "mcpServers": { "hireme-mcp": { "url": "https://mcp.djaouad.tech/mcp" } } }
Built by Djaouad Frih — this server is itself the demo of what he ships.
Demo
Frequently asked questions
What is HireMe MCP?
The first portfolio AI agents can hire. Profile, products, pricing and briefs over MCP.
How do I install HireMe MCP?
It runs as a remote server. In Claude Code: claude mcp add --transport http hireme-mcp 'https://mcp.djaouad.tech/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does HireMe MCP need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is HireMe MCP open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains HireMe MCP?
It is published by djoudad292. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.