How the Infrastructure Works
Two kinds of plumbing — custom connectors that give agents tools, and shared database schemas that give them governed memory.
Two kinds of plumbing
Agents are only as capable as what they can reach. Two things make the difference: the connectors that hand them tools, and the databases that give them a shared, governed memory.
Connectors (MCP servers) expose a tightly-scoped set of tools — only the endpoints we want an agent to have. Database schemas are where agents read and write structured information, with access controlled so each one can only touch its own area.
What's here
11 custom connectors
One per service we work with — context, tasks, storage, image generation, email, calendar, social, billing, nonprofit research, and network control.
Purpose-built schemas
Design, products, forms and consent, the publication, the social pipeline, interview records, the knowledge base, link attribution, and CRM prospecting.
Governed by default
Every table has row-level security on; agents reach data through a controlled path, not a master key.
How the connectors get built
Every connector is built with FastMCP and Python by our MCP agent, to spec. Hands-on direction is usually under thirty minutes — agents are genuinely good at building these.
The point of a custom connector isn't the code; it's the design. Instead of a long instruction file, an agent gets a short one and a clear set of tools — custom descriptions, only the endpoints we want, and the occasional extra gate — tuned to exactly what the work needs. Nothing more, nothing less.
You don't need all of this to start
Most of what these agents rely on has a simpler equivalent. Anywhere we use a database, you can usually start with a spreadsheet or a document — whatever you're comfortable with. Anywhere we built a custom MCP server, you can reach for a prebuilt AI connector instead of building your own.
We go further because it's where our experience pays off. Years of hands-on database work make a custom data layer feasible for us, and purpose-built MCP servers let us hand each agent a short, sharp instruction file and exactly the tools it needs — custom descriptions, only the endpoints we want, and the occasional extra gate — instead of a long manifesto or playbook. Nothing more, nothing less.
Ready to build technology that works for your mission?
Tell us where your organisation is and what's slowing your team down. We respond personally.