Browse categories
Explore
Fiverr Pro
English
$
USD
I will fix your broken ai agent, mcp server, or automation
Devan
About this gig
Something in your AI agent, MCP server, or automation pipeline is broken, and you have either lost the person who built it or spent hours staring at logs that do not make sense. That is what this gig is for.
I work across the stack this usually breaks in: Agentic sessions, Claude Code configurations, MCP server connections, agent tool-calling logic, and the plumbing between them (auth, permissions, malformed responses, silent failures).
What you get:
- A clear diagnosis, not just a patch: you will know what actually broke.
- A working fix, tested against the failure case you describe.
- At Premium: documentation so the same failure is easier to catch next time.
What I need from you: the error/symptom (logs, screenshots, or a description of
what is happening vs. what should happen), and access to the relevant code/config.
The clearer the reproduction, the faster the turnaround.
Get to know Devan
Devan
Daily stack: MCP servers, Claude Code setups, Autonomous agents
- FromCanada
- Member sinceSep 2013
- Avg. response time1 hour
Languages
English
I build infrastructure for AI agents: MCP servers that connect Claude to real tools and data, Claude Code setups for dev teams, and autonomous agents that run workflows unattended.
Coding since 2013, but I only started taking gigs seriously this year.
I run this stack daily on my own multi-agent platform: queued tasks, isolated execution, a review gate before anything merges.
Fast responder, clear about scope before I start, and I will tell you honestly if your project is not a fit.
My Portfolio
FAQ
I do not know what is wrong, just that it is not working. Is that OK?
Yes, that is most requests. Send whatever you have (error messages, logs, or just "it used to do X and now it does Y") and I will take it from there.
Can you fix something built by someone else, in a stack I do not fully understand?
Yes, that is common. I will ask clarifying questions if the intended behavior is not obvious from the code.
What if the fix needs more than the package I ordered covers?
I will tell you upfront before doing extra work. No surprise scope creep. If it is bigger than expected, we adjust the package or scope together.
Is this only for Claude-based systems, or other LLM agents/automations too?
Primarily Claude/Claude Code and MCP-based systems, since that is my daily stack. Message me with specifics if it is a different LLM stack and I will tell you honestly what the best course of action to take.
