post_a_job — Teppek MCP Prompt

post_a_job is one of 5 prompts on the Teppek MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke post_a_job from your client

• Claude Code Teppek Prompt/post_a_job run in your project directory
• Claude Desktop Teppek Prompt/post_a_job ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Teppek Prompt/post_a_job ~/.cursor/mcp.json
• VS Code Teppek Prompt/post_a_job .vscode/mcp.json
• Zed Teppek Prompt/post_a_job ~/.config/zed/settings.json
• Windsurf Teppek Prompt/post_a_job ~/.codeium/windsurf/mcp_config.json
• Cline Teppek Prompt/post_a_job ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Teppek Prompt/post_a_job ~/.gemini/settings.json
• Grok Teppek Prompt/post_a_job .mcp.json (in your project root)
• ChatGPT Teppek Prompt/post_a_job Settings → Connectors → Advanced → Developer mode
• Claude.ai Teppek Prompt/post_a_job Settings → Connectors → Add custom connector
• LangChain Teppek Prompt/post_a_job pip install langchain-mcp-adapters

Other prompts on this server

• rent_out_property
• sell_my_vehicle
• offer_a_service
• find_near_me

Teppek also offers 2 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.