Skip to content
bpBrandon Perez

About

From the support desk to intelligent integrations

I design and develop integrations that bridge AI assistants, enterprise systems, and developer platforms. My work explores secure API connectivity, intelligent workflows, MCP infrastructure, and the next generation of AI-powered tools.

Journey

How I got here

My path runs from hands-on enterprise support into automation, integration engineering, and AI systems. Each step built on the one before it.

  1. Enterprise IT & desktop support

    Supporting people and endpoints in large environments: troubleshooting hardware, software, identity, and network issues where downtime has real cost. This is where I learned how enterprise systems actually behave.

  2. Automation

    Repeated tickets became scripts, and scripts became workflows. Application deployment, uninstalls, and standard fixes are better automated, documented, and auditable.

  3. Integration engineering

    Connecting systems through REST APIs, secure authentication, and careful error handling: the unglamorous work that makes integrations dependable.

  4. AI & agentic systems

    Now: bringing AI assistants into that world safely through Model Context Protocol, so tools are exposed deliberately, with authentication, authorization, and observability built in.

Strengths

What I bring to a problem

  • Understanding complex enterprise environments

    Many systems, many owners, real constraints. I map how things actually connect before changing them.

  • Turning operational problems into automation

    I start from the ticket queue and the manual steps, then automate what is repetitive and risky.

  • Building dependable API integrations

    Official APIs, least-privilege access, token refresh, and clear failure handling, tested step by step before anything ships.

  • Integrating AI with existing systems

    Connecting assistants to the tools people already use instead of replacing them.

  • Security, reliability, maintainability

    Least privilege, no secrets in code, clear logs, and designs the next engineer can understand.

Technology

Stack & tooling

Tools I work with, honestly labelled: Using means used in real work or projects; Learning means actively studying or experimenting.

Languages & runtimes

  • Python(using)
  • JavaScript(using)
  • TypeScript(learning)
  • Node.js(learning)

APIs & protocols

  • REST APIs(using)
  • Model Context Protocol (MCP)(using)
  • API testing & collections(using)

Security & identity

  • Standards-based authentication(using)
  • Identity & access management(using)
  • Least-privilege design(using)

AI & platforms

  • LLM assistants & APIs(using)
  • AI agents & automation(using)
  • Enterprise SaaS platforms(using)
  • API gateways(using)

Infrastructure & tooling

  • Git(using)
  • Windows (enterprise)(using)
  • Endpoint management(using)
  • Docker(learning)