MCP Connectors
MCP connectors on the blog.
How a language model reaches the systems where the work actually happens.
What this topic covers
The Model Context Protocol defines how a language model talks to another system’s tools, data sources, and prompts. For a company, that is the layer that matters: without it a model answers general questions, with it your questions about your own order book.
These posts walk the path from architecture to a running connection. They name the layers, the permission model, the audit trail behind every call, and the places where integrations reliably get stuck.
What we learned about MCP integrations is condensed in the Lab’s lessons learned.
Go to the MCP integration lessonsPosts on this topic 2 posts
Connecting CRM and ERP to a language model in four layers
Why point-to-point integration collapses at the third data source, how an MCP service mediates instead, and the setup times we measured in completed projects.
6 min read
Building your own MCP server that survives production
When a custom MCP service is worth it, what the protocol looks like on the wire, how to describe a tool, and five rules that decide a connector’s quality.
7 min read