Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix your claude code, claude cowork, open claw or mcp server setup
Jessy Mariau
About this gig
Claude Code won't start. Your Claude Cowork task never fires. Your mcp server connects, then quietly drops. OpenClaw is installed but the agent can't see any tools. ClawDBot throws an error with exactly zero useful search results.
I run this stack daily, so I've usually hit it before.
Send me the error and your config and I'll fix one specific install, config or connection problem, then write up what was actually wrong so it doesn't catch you twice. The config comes back in a state you can read.
The usual suspects, for what it's worth: an mcp server registered but exposing no tools, the wrong transport for the client, permission errors on Windows, a config pointing at a path that moved, environment variables not reaching the process. Rarely the interesting bug you were hoping for.
I maintain Booboo, an open-source operational brain with its packages on npm and a listing on the official MCP registry, and I wire mcp servers into my own tools every day.
If it turns out to be a five-minute fix, I'll say so.
Get to know Jessy Mariau
Jessy Mariau
I build web scrapers, automations and the UI on top of them
- FromUnited Kingdom
- Member sinceFeb 2024
- Avg. response time1 hour
Languages
English, French
Three businesses run on my own automation fleet: 40+ jobs a day across 27 n8n workflows. I build web scrapers too. They run on Apify on a schedule and feed your sheet or CRM, and eleven of mine are public on the Apify Store for you to try. When the data needs a face, I design the dashboard or site around it. Zapier made me an Authorized Solution Partner (Silver), though most of my builds run in n8n with Claude or GPT doing the reading. I'm UK-based and agree a fixed scope before any work starts.
My Portfolio
FAQ
What do you need from me to start?
The error message or a screenshot of it, your config file, and which OS and client you're on. That's usually enough to spot the problem before I touch anything.
Do you need access to my machine?
In most cases I don't need it. I diagnose these from the config and the error text, and you get the corrected file back with a short written note on what was wrong. If a live screen-share is the only way, I'll ask first.
What counts as one fix?
One problem end to end: one server that won't connect, one install that won't run, one config being ignored. If there turn out to be three unrelated problems, I'll tell you up front.
What if it turns out not to be fixable?
Some things aren't fixable from a config: a broken upstream package, an OS setup the tool doesn't support. If I hit one, I'll tell you what's wrong and why, quickly, rather than sit on it.
