# Develop21 MCP MCP Server > **Develop21 MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Develop21 MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/develop21-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About AI-powered job search and application tracking for AI Assistants. Search jobs across major job boards and company career pages, build personalized shortlists, evaluate job fit, tailor resumes and cover letters, and track applications from submission through interviews and offers. --- ## Details - Server ID: `develop21-mcp` - Version: 0.18.0 - Tools: 23 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Develop21 MCP has to be in the toolset first. In order: 1. Add Develop21 MCP to your toolset at https://mewcp.com/mcp/develop21-mcp 2. Connect your Develop21 MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (23) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `develop21_user_state` _(read)_ — The starting point of a Develop21 thread - typically the first call, and the answer whenever the user asks what's going on, where they are, or what to do next.… - `develop21_ping` _(read)_ — Use when the user wants to test or verify their Develop21 connection ("test Develop21", "is Develop21 connected?"). Optionally send a short note. Returns a… - `develop21_rate_response` _(write)_ — Report a problem with, or suggest an improvement to, a Develop21 response - use when a tool did not work as described (bug, data issue) or you see a concrete… - `develop21_save_document` _(destructive)_ — Use when the user wants Develop21 to keep a document - resume, cover letter, profile notes, or a review verdict. Send name, doc_type and full content (plus… - `develop21_get_document` _(read)_ — Use when the user wants a document previously saved to Develop21 ('get my saved resume', 'read back X', 'what documents do I have?'). Send name or id for one… - `develop21_create_profile` _(write)_ — Use when a new user wants to set up Develop21, shares a resume, or says 'create my Develop21 profile'. Extract whatever fields you already have evidence for… - `develop21_update_profile` _(destructive)_ — Use when the user shares new or changed career information - new role, new preferences, corrected details - or asks to review what Develop21 knows about them… - `develop21_get_profile` _(read)_ — Download the complete stored career profile - every field value, plus the briefing, optionally the full resume text. Use when a task needs the whole profile,… - `develop21_review_job_fit` _(write)_ — Use when the user shares a job posting or asks whether a job suits them ('review this job', 'am I a fit?', 'should I apply?'). Send title, company and the FULL… - `develop21_record_reviews` _(write)_ — Use right after reviewing one or more jobs with develop21_review_job_fit, to SAVE the verdicts so they are not lost. Send a reviews array; each: opportunity_id… - `develop21_triage_job_captures` _(read)_ — Use when the user wants to quickly sort through the jobs they've captured but not yet reviewed ('triage my captures', 'sort my saved jobs', 'which of these are… - `develop21_get_job` _(read)_ — Use when the user asks about jobs saved to Develop21 ('what jobs have I captured?', 'the job I sent from the extension', 'review my latest capture'). Send… - `develop21_help` _(read)_ — Use when the user asks what Develop21 can do or how to do something with it ('how do I delete a document?', 'can Develop21 track my applications?', 'what is… - `develop21_delete_document` _(destructive)_ — Use ONLY when the user explicitly asks to delete a document saved to Develop21 ('delete my old cover letter', 'remove the acme review'). Send name or id.… - `develop21_delete_job` _(destructive)_ — Use ONLY when the user explicitly asks to remove a job saved to Develop21 ('delete that Acme job', 'remove the listing I captured'). Send id or title. Deletes… - `develop21_log_application` _(write)_ — Use when the user REPORTS an application outcome in conversation - applied ('I sent it', 'just applied'), deciding to pass, waiting on a response, or hearing… - `develop21_tailor_resume` _(read)_ — Use when the user wants their resume/CV tailored for a SPECIFIC job they've reviewed ('tailor my resume for the Acme role') - typically after a Go decision.… - `develop21_update_master_resume` _(read)_ — Use when the user wants to improve their master resume with no specific job in play ('update my master resume', 'improve my CV'), or to BUILD the master resume… - `develop21_draft_cover_letter` _(read)_ — Use when the user wants a cover letter written or improved for a job ('now the cover letter', 'help with my cover letter') - typically after tailoring the… - `develop21_check_document` _(write)_ — Use at document completion to run the AI-writing check, and when the user pastes back a pangram.com result link. action:'prepare' returns the check pack - the… - `develop21_favourite_job` _(write)_ — Use when the user wants to protect a saved job ('favourite the Acme role', 'keep that one safe') or release one ('unfavourite it'). Send id or title, and… - `develop21_plan_job_search` _(destructive)_ — Use when the user wants to find new or more jobs, or none of their saved jobs fit. Develop21 compiles starting queries from the career profile for job-search… - `develop21_execute_job_search` _(write)_ — Use when the user wants to RUN their saved job searches - the daily loop ('run my job searches', 'run my saved searches'). action:'list' returns the saved… --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization: Bearer API_KEY" ] } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file and restart Claude Desktop 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)