We set up Claude Code for your developers and repositories, and connect Claude to the tools your business uses through MCP servers: configuring existing ones, building new ones for your own systems, and keeping access to what each person needs.
Tell us what you needSee typical projectsYou describe it. We build it.
What we hear from businesses before a project like this starts.
The requests that come up most often for this kind of work, and what each one takes to work properly.
The vendor's MCP server, or a small one we build, configured with read-only access unless you need more.
Installed, authenticated, and tested with real requests so you know what it can and can't do.
A server that exposes your internal API or database as a small set of well-described tools.
Project instructions, permissions, hooks and commands, so it works the way your team works.
A working session on how to use Claude Code and MCP well in your setup, with written notes afterwards.
One shared configuration, rules for secrets and permissions, and a short guide for each developer.
Tools that come up most: Claude Code, Model Context Protocol, Claude Desktop, HubSpot, QuickBooks, Xero, Salesforce, GitHub, Python, TypeScript.
Concrete pieces, each one something you can open and check when it's done.
Project instructions, allowed commands, hooks and shared settings checked into the repository.
CLAUDE.md, settings, hooks, slash commandsExisting MCP servers installed, authenticated and tested for your team.
Local and remote MCP servers, OAuthA server that gives Claude a small, well-described set of tools for your own system.
MCP SDK in Python or TypeScriptEach connection limited to the data and actions it needs, with secrets kept out of the repository.
Scoped API keys, read-only roles, secret storesOne configuration for everyone, with a short guide and a session for the team.
Shared settings, documentationEach tool tested with real requests, including the ones that should be refused.
Test scripts, logsExample packages to show the shape of the work. These are examples, not past clients; yours gets its own written scope.
Example package
Claude Code or Claude Desktop connected to HubSpot, QuickBooks or Xero through an MCP server.
You get
Example package
Claude Code set up for one codebase and your team's way of working.
You get
Example package
An MCP server for your own API or database, with a small set of tools.
You get
Example package
An existing Claude Code and MCP setup reviewed for access and reliability.
You get
Lumen Home Goods was answering the same order-status and returns questions hundreds of times a week. We built a support assistant that runs on the website chat, email and the Shopify inbox. It looks up the customer's actual order and live carrier tracking, answers only from the store's own policies and product pages, and can take approved actions such as creating a replacement order or a return label. Refunds over a set amount, angry customers and anything it isn't sure about go to a person with the full conversation attached.
Python, Claude API with tool use, retrieval over store docs, Shopify Admin API, carrier tracking APIs, PostgreSQL, React widget
Hollow Oak's operations and engineering team wanted to ask questions of their order and warehouse data in plain English, and to act on the answers without switching tools. We built a custom MCP server that gives Claude safe access to their systems: read-only queries against a database replica, with PII masked, plus a small set of write actions such as refunds and Slack posts that need human approval. We also set up Claude Code for the whole team: shared MCP config, a project CLAUDE.md, slash commands and hooks, all checked into the repo.
Python, Model Context Protocol SDK, PostgreSQL (read replica), Slack and Linear APIs, Claude Code, Docker
A working example we built to show this kind of work. It is a demonstration, not a client project.
Sample build
An MCP server with three tools over an inventory dataset: item lookup, a low-stock report with suggested reorder quantities and cost, and stock adjustment. A demo client connects over stdio, lists the tools and calls each one. The README includes the Claude Code / Claude Desktop config.
Python 3.12, MCP Python SDK (FastMCP), stdio transport, SQLite
About the screenshot: A transcript of a demo client calling each tool over sample inventory data.
The habits that keep this kind of project from going wrong.
Every connection starts read-only and limited to what the scope needs. Write access is added only where you ask for it.
API keys and tokens live in your secret store or environment, never in the repository.
We test what each tool should refuse to do, not only what it should do.
You get a plain record of what is connected, what it can reach, and how to switch it off.
You know what you're getting before work begins, and you see it working at every milestone.
Tell us what you need in your own words, and which tools you already use. A few lines is plenty to start.
We reply with a short written scope: what gets built, what is out of scope, which accounts we need, and how we'll both know it works. You know what you're getting before work begins.
The work is split into milestones. At each one you see it working in your own account and sign it off before we go on.
You get the working system, its documentation and a walkthrough. If anything we built breaks in the next 30 days, we fix it at no charge.
Pushbuild has built software for businesses since 2010, for more than 40 clients. Every project is led by a former public-company CTO, from Groton, Massachusetts. See products we've built.
It can be, with the right limits. We start read-only, scope each key to what it needs, and show you exactly what is connected before anyone uses it.
That depends on how your team will use it. We tell you in the scope which plan or API access each part needs; the subscription is in your name.
You do. Configuration lives in your repositories and accounts, and custom servers are in a repository you own.
Only to set up and test the connections, using accounts or keys you create for us. Remove them at handover.
A single connection or repository setup usually takes a few days; a custom MCP server or team rollout one to three weeks.
For 30 days we fix anything we set up that does not work as the scope describes, at no charge. After that, changes are written up and agreed with you before we begin.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com