Technical
For engineering teams
How we design, secure and run MCP servers and automations.
Stack
- MCP servers in TypeScript or Python with the official SDKs. Transport: stdio for local use, Streamable HTTP for remote servers.
- Workflows in n8n (self-hosted or cloud), Make or Zapier, plus code steps where needed.
- Hosting on your cloud or ours: containers, serverless functions or Cloudflare Workers.
Security
- OAuth 2.1 or scoped API keys. No shared admin credentials.
- Least privilege: each tool gets only the access it needs. Read-only by default.
- Input validation on every tool, and rate limits.
- Audit logs of every tool call.
Process
- Scope. We list the tools, their inputs and outputs, and the risks.
- Build. Tests for each tool, and evaluation runs against real prompts.
- Review. Your team reviews the code. You own the repository.
- Run. Monitoring, alerts and updates, or a clean handover with docs.
Working with your team
We work in your repo, follow your conventions and open pull requests. Pairing sessions are welcome.