I will build a tested custom python mcp server


About this gig
Turn a repetitive local task into a tested MCP tool your AI client can call.
I build custom Python MCP servers with 1-3 deterministic tools from your public specification and sanitized examples. Good fits include data validation, local file checks, checksum manifests, and structured-output utilities.
Every package includes:
- Python source and an installable package
- Local stdio MCP configuration and run instructions
- Tests for valid, invalid, and edge-case inputs
- A real local tool-call transcript
- Acceptance checks matched to your fixtures
A separate internal QA review reproduced 36/36 tests and a real local stdio call for the studio reference build. Your project receives its own tests; client results are not guaranteed.
Scope: local stdio only. Hosting, OAuth, Docker, production credentials, multi-user access, and unverified live integrations are excluded.
Before ordering, send your task, public spec, sanitized input/output examples, and target environment. I will confirm fit, acceptance criteria, and availability. Do not send secrets.
Get to know Engineer Tsai
AI Automation and Reliability Services
- FromTaiwan
- Member sinceAug 2026
Languages
Chinese, English
My Portfolio
FAQ
What transport does the server use?
Local stdio only — you run it as a subprocess from your own MCP client config. No REST API, no hosting, no always-on server.
Can you add OAuth, user accounts, or handle my API keys?
No. This Gig excludes authentication, multi-user access, and secret custody. The server has no surface for credentials; those needs require a separate scope.
Will you deploy this to the cloud or Docker?
No. Hosting and container packaging are excluded. You run the delivered local stdio server yourself.
How will I verify that the tools work?
Every delivery includes tests built from your valid, invalid, and edge-case fixtures, plus MCP protocol tests and a sample local stdio call transcript.
Is a checksum or file-hashing tool unique to this service?
No. Common utility-tool shapes already exist. The value is your custom bundle, tests, documentation, and reproducible evidence—not exclusivity of a generic tool concept.
What if my project exceeds the 3-tool local stdio scope?
Message me before ordering. Hosting, OAuth, multi-user auth, secret custody, Docker, unsupported integrations, or more than 3 tools require a separate scoped order.

