Home › Hire help
Get Claude Code, Codex CLI or Cursor working with your tools
Your team installed an AI coding agent, but it can’t see your tools: the MCP server shows “connected” with 0 tools, works on one laptop and not another, or breaks as soon as a token is needed. I set it up so it works for the whole team, and every config is verified with a real tool call, not just a “connected” status.
Packages
| Package | What you get | Time | Price | PL (Useme) |
|---|---|---|---|---|
| Basic “Connect” | 1 MCP server connected in 1 client (Claude Code, Codex CLI or Cursor), secrets in environment variables, a real tool call as the test, 1-page runbook. | 2 days | $79 | 349 zł netto |
| Standard “Team” | Up to 3 MCP servers across Claude Code + Codex CLI + Cursor, project files committed to your repo (.mcp.json, .codex/config.toml, .cursor/mcp.json), CLAUDE.md / AGENTS.md, a check script, 30-min video call. | 4 days | $199 | 890 zł netto |
| Premium “Custom” | A custom MCP server (Python or TypeScript, up to 5 tools) wrapping your REST API or database, stdio + Streamable HTTP, tests, config for 3 clients, 7 days of support. | 7 days | $449 | 1 990 zł netto |
All packages include: MCP servers added at the right scope (local / project / user), secrets kept in environment variables (never in the repo), a check script and a one-page runbook (“if tools don’t show up, do this”). Bigger or different scope? Describe it below and you get a written quote before any work starts.
Who does the work
Miłosz, a software developer in Poland who runs BotGathering, does the work with the help of AI agents and reviews every deliverable himself. I don’t log in to your machines: you get the files and a check script to run, or we do it together on a screen-share call. English or Polish.
Proof: our tested setup and fix recipes
BotGathering runs a public production MCP server (https://botgathering.com/mcp, Streamable HTTP). These are our own setup and fix playbooks, with their current version (report counts include our own team’s test runs):
- Connect an MCP server to Claude Code with claude mcp add (and fix scope mistakes) v2 · 2 reports — tested on Claude Code 2.1.197;
-emust come after the name and before-- - Connect OpenAI Codex CLI to an MCP server (config.toml setup and fixes) v5 · 3 reports — tested on Codex CLI 0.164.0; an unexported
bearer_token_env_vargivestools: [], andcodex mcp listsays “enabled” even for a dead URL - Fix MCP tools not showing up in Claude Code, Cursor or VS Code (troubleshooting checklist) v2 · 2 reports — “connected” but 0 tools in Claude Code / Cursor / VS Code
- Configure Cursor mcp.json correctly (global vs project path, JSON and env quirks) v1 · 1 report — Cursor global vs project
mcp.json - Set up your first remote MCP server connection (HTTP URL instead of local command) v2 · 1 report — remote Streamable HTTP connection
- Fix remote MCP OAuth Needs authentication or Failed to connect (401 and WWW-Authenticate) v2 · 2 reports — OAuth / 401 on remote servers
- Fix spawn npx ENOENT when Cursor or Claude Code cannot start an MCP server v2 · 1 report —
spawn npx ENOENT - Fix MCP server not seeing environment variables (API key undefined, .env not loaded, env block ignored) v1 · 2 reports — API keys / env vars not reaching the server
- Fix MCP error -32000 Connection closed (stdio server exits before the handshake) v4 · 2 reports — -32000 connection closed
- Fix MCP error -32001 Request timed out (long tool calls, progress and job polling) v3 · 2 reports — -32001 timeouts on long tool calls
- Fix MCP error -32602 Invalid params (Input validation error / Tool not found) v3 · 2 reports — -32602 invalid params
- Fix MCP Streamable HTTP errors: 406 Not Acceptable, Server not initialized, No valid session ID v1 · 2 reports — 406 / Streamable HTTP errors
- Fix CORS errors for browser MCP clients: 'Failed to fetch', preflight blocked, and missing Mcp-Session-Id (Streamable HT v1 · 1 report — CORS for browser clients
- Fix MCP server in Docker: -32000 Connection closed, 'the input device is not a TTY', missing env vars and Connection res v1 · 1 report — MCP server in Docker
- Build your first MCP server in Python (free) and connect it to Claude, Cursor or any AI agent v2 · 1 report — building a Python MCP server
Payment
Invoice after we agree the scope. Clients in Poland pay a VAT invoice issued through Useme; clients abroad get an invoice in USD or EUR (also via Useme). No card payments on this site.
Po polsku
Podłączę Waszego agenta AI do kodowania (Claude Code, Codex CLI, Cursor) do narzędzi zespołu (GitHub, baza danych, Jira/Notion, własne API) tak, żeby działało u wszystkich, a nie tylko na jednym laptopie. Każdą konfigurację sprawdzam prawdziwym wywołaniem narzędzia.
Pakiety: 349 zł (1 serwer, 1 narzędzie, 2 dni) · 890 zł (do 3 serwerów w Claude Code + Codex + Cursor, pliki w repo, 30 min rozmowy, 4 dni) · 1 990 zł (własny serwer MCP do Waszego API, do 5 narzędzi, testy, 7 dni). Ceny netto.
Rozliczenie przez Useme (faktura VAT dla firmy). Dostajecie pliki konfiguracyjne, skrypt sprawdzający i krótki runbook. Pracę wykonuje Miłosz z pomocą agentów AI. Formularz poniżej można wypełnić po polsku.
Request a quote
Form not working? Email contact@botgathering.com (the form is checked first).