Eight Mile · AI integration · MCP integration
Your systems, inside the assistant you already use.
The Model Context Protocol is how an assistant like Claude, ChatGPT or Copilot reaches outside its chat window. We build MCP servers in front of your ERP, CRM, helpdesk and internal databases, so your team can ask about an order, a customer or a contract where they already work — and every call goes through a key you can name, scope and revoke.
What we build
MCP integration, built as software.
MCP servers for your systems
A server that speaks the Model Context Protocol in front of your ERP, CRM, helpdesk or database, exposing a small set of well-named tools rather than raw tables.
Scoped, revocable keys
Each person or service gets its own key. Only a hash is stored, each key carries the scopes it was granted, and a revoked key stops working on its next call.
A record of every call
Which key called which tool, with what arguments, and when: the record a security team asks for before anything is connected.
Workflow automation
Tools that act as well as read — raise the ticket, draft the article, update the record — each behind a scope that has to be granted explicitly.
How it works
The same steps, in the order they run.
01
Choose the tools
We start from the questions your team asks and expose the handful of tools that answer them, not every endpoint you have.
02
Scope the access
Nothing can change data by default. Write tools sit behind named scopes, and every tool enforces the same boundaries your own application does.
03
Connect the assistant
The server is added to Claude, ChatGPT or Copilot with a key made for that person or service, and works in the tool they already have open.
04
Review and revoke
Keys are listed with when each was last used, and any one can be revoked without touching the others.
Controls
What makes it safe to ship.
Decided before the first prompt is written, and tested like the rest of the code.
Read-only unless granted
A new key can change nothing. Write access is a scope granted when the key is made, never a default.
One organisation, one boundary
A key is verified inside the organisation it belongs to, and every query it makes is held to that organisation’s data.
Only the hash is kept
The key is shown once when it is made and stored as a hash, so a copy of the database does not hold a working key.
A cap on live keys
A small limit on active keys keeps the list short enough to read, and a leaked key easy to find.
Proof
Where you can see it working.
Our own products, each with a page of its own that shows how it is built.
Straight answers
The questions people ask about it.
The rest of our AI work
Next step
Tell us which system your team wants to ask questions of.
Name the system, what people look up in it and who should be allowed to change things. We will tell you which tools an MCP server for it should expose.