draft_job_post — GigNGo Local Services Marketplace MCP Tool
draft_job_post
(draft job post) is one of 10 tools on the
GigNGo Local Services Marketplace
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call draft_job_post from your client
- Claude Code GigNGo Local Services Marketplace draft_job_post run in your project directory
- Claude Desktop GigNGo Local Services Marketplace draft_job_post ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GigNGo Local Services Marketplace draft_job_post ~/.cursor/mcp.json
- VS Code GigNGo Local Services Marketplace draft_job_post .vscode/mcp.json
- Zed GigNGo Local Services Marketplace draft_job_post ~/.config/zed/settings.json
- Windsurf GigNGo Local Services Marketplace draft_job_post ~/.codeium/windsurf/mcp_config.json
- Cline GigNGo Local Services Marketplace draft_job_post ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GigNGo Local Services Marketplace draft_job_post ~/.gemini/settings.json
- Grok GigNGo Local Services Marketplace draft_job_post .mcp.json (in your project root)
- ChatGPT GigNGo Local Services Marketplace draft_job_post Settings → Connectors → Advanced → Developer mode
- Claude.ai GigNGo Local Services Marketplace draft_job_post Settings → Connectors → Add custom connector
- LangChain GigNGo Local Services Marketplace draft_job_post pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http gigngo https://gigngo.org/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.