MCP for agencies, one server per client
Run MCP Self-hosted once. Connect Claude to each client’s WooCommerce store, WordPress site, database or inbox. Give every team member their own seat, without a separate SaaS subscription per client.
3 seats included · extra per client at € 18,15 excl. VAT: € 15,00/yr
One license, every tool a client's stack needs
Built for how agencies actually work
Per-client licensing
Each client’s license, seats and activations stay separate from every other client’s. Nothing crosses between accounts.
Seats for your team
Add a seat for each team member who needs access. Revoke it when they leave the project.
Self-hosted per engagement
Run MCP Self-hosted in a client’s own Docker environment when the contract requires it. Nothing goes through a shared cloud.
Every tool, one license
License only the add-ons a client’s stack really needs: Missive, WooCommerce, Database, Brain, WordPress.
From proposal to running server
No in-house infrastructure team needed.
Buy MCP Self-hosted for the client
€ 217,80 excl. VAT: € 180,00/yr, with 3 seats and 1 activation. That is enough for most single-client projects.
./mcp-update.sh
Unzip the download in the client’s environment (or yours), fill in the .env and run ./mcp-update.sh. It logs in to the registry, pulls the images and starts mcp-core.
Add the tools the stack needs
License WooCommerce, WordPress, Database, Missive, Brain, Lightspeed eCom or Plesk one by one, from € 72,60 excl. VAT: € 60,00/yr per tool.
Hand over or keep managing
Add a seat for the client’s own team, or keep the one activation under your agency’s control.
Seats and activations are two separate dials
Activations set how many mcp-core containers can run under one license. Seats set how many people can connect to a running container. Scale either one as a project grows.
How licensing works
Managing five clients with MCP
Wiring up each client yourself vs. MCP Self-hosted
| Build it yourself per client | With MCP Self-hosted | |
|---|---|---|
| Setup per client | Custom integration code | ./mcp-update.sh |
| Licensing | Tracked by hand per contract | One license per client, seats and activations built in |
| Tool coverage | Build and maintain your own connectors | 6 ready-made tool add-ons |
| Keeping licenses current | By hand | docker exec mcp-core npm run refresh-license |
What does MCP for agencies look like in practice?
MCP for agencies means one self-hosted server that gives Claude controlled access to the systems your clients run: their WooCommerce store, their WordPress site, a database or a shared inbox. That server is mcp-core. It runs in Docker, on your infrastructure or on the client’s. Your team connects through Claude Desktop or Claude Code, and every person gets their own token.
The Model Context Protocol is the standard Claude uses to call external tools. MCP Self-hosted speaks it over Streamable HTTP, with legacy SSE for older clients, so any MCP client that supports Streamable HTTP or SSE can connect. New to the protocol? Read what MCP is and how it works first.
Which client work can Claude take over with MCP?
The value of MCP for agencies sits in the small, repetitive tasks that eat retainer hours. With the current add-ons, Claude can handle work like this:
- WooCommerce: look up an order, check a customer’s order history, find products that are low on stock.
- WordPress: list posts and pages, check menus, widgets and installed plugins, or draft a page once write mode is on.
- Database: list tables, describe a table and run a query against a client’s MySQL, MariaDB or PostgreSQL database.
- Missive: look up conversations per customer and read threads and tasks in your agency’s shared inbox.
- Brain: keep project notes per client in a markdown vault that Claude can search and update.
Claude works on live data at the moment you ask. That is the daily case for MCP for agencies: nobody exports a CSV first, and nobody logs in to five admin panels to answer one question.
How do you set up MCP for agencies across several clients?
There are two ways to structure it. Pick one per engagement.
One license per client. Buy MCP Self-hosted for each client and run one mcp-core container per client. Each license has its own entitlements, its own seats and its own activation. Access and billing stay separate. This is the right fit when a contract requires the server to run inside the client’s own environment.
One server, several stores or sites. The WooCommerce and WordPress add-ons accept several targets through WOOCOMMERCE_CONNECTIONS and WORDPRESS_CONNECTIONS. Claude then picks the store or site by its id. This suits an agency that runs a group of related sites itself and wants one place to manage them.
How do seats and activations work for an agency team?
An activation is one running mcp-core container. A seat is one person or device that connects to it. MCP Self-hosted includes 1 activation and 3 seats. Each seat has its own token, its own subset of tools and its own setting per tool: read-only or Can make changes.
This is where MCP for agencies differs from one shared admin login: access is scoped per person. A junior developer gets read-only access to a client database. The project lead gets Can make changes on WordPress. When someone rolls off the project, you revoke their seat in My Account → MCP Self-hosted. It stops working once MCP Self-hosted picks up the change (at the next license check, or right away with refresh-license), and every other seat keeps running. The details are in setting up multiple seats.
Is MCP for agencies safe with client systems?
Yes, if you start read-only and widen access on purpose. Every tool except Brain defaults to read-only, and you choose Can make changes per tool when you add a seat in My Account → MCP Self-hosted. In read-only mode the write tools are not registered, so Claude cannot call them.
Login details stay in the .env file on the server that runs mcp-core. Claude never receives the WooCommerce API keys, the WordPress application password or the database password. It only sees the tools MCP Self-hosted exposes. For databases, combine read-only mode with a database user that has SELECT rights only.
Licensing is checked inside the container. On start and periodically, MCP Self-hosted checks its license with AddoCore and receives its entitlements. A tool without an entitlement is not exposed at all. If AddoCore cannot be reached, a 96-hour grace period keeps everything running.
What are the setup steps per client?
The steps for MCP for agencies are the same for every client, which keeps the routine easy to hand over within your team.
- Buy MCP Self-hosted and the add-ons that match the client’s stack.
- Download the zip from My Account. It holds
docker-compose.yml, a pre-filled.env,.env.registryandmcp-update.sh. - Fill in the login details for each tool in
.env. - Run
./mcp-update.sh. It logs in to the AddoCore container registry, pulls the image and starts mcp-core. - Hand each team member a seat token and add the server in Claude Desktop or Claude Code.
Updates use the same command. MCP_VERSION sets the version, so you decide when each client’s server moves to a new release. The full walkthrough is in the Docker Compose install guide.
A tool bought later needs no reinstall and no new download. It is added to the license. Run the refresh below or wait for the next check, and you get an email listing the env vars the tool needs.
docker exec mcp-core npm run refresh-licenseWhat does MCP for agencies cost?
MCP Self-hosted costs € 217,80 excl. VAT: € 180,00 per year and includes 3 seats and 1 activation. Add-ons start from € 72,60 excl. VAT: € 60,00 per year; the price differs per add-on. An extra seat is € 18,15 excl. VAT: € 15,00 per year. Payment is yearly recurring through Mollie, and EU VAT is handled at checkout with B2B reverse charge. Some products can be billed monthly with a 12-month minimum term.
If a client does not want to run Docker at all, the MCP Hosted seat is the alternative. AddoCore runs the server, billing is monthly and the first month is free.
MCP for agencies works best as a repeatable routine: the same install per client, read-only defaults and one seat per person. Start with MCP Self-hosted for your first client and add tools as the work asks for them.
Veelgestelde vragen
No. Skills are separate, free downloads — no license or entitlement required.
Yes, per tool and per seat. You choose read-only or Can make changes for each tool when you add a seat in My Account → MCP Self-hosted. Every tool defaults to read-only except Brain, which can make changes from the start. See entitlements vs tool modes.
Yes. Copy the whole install folder, including ./state, and the activation moves with it, because the instance id lives in that folder. On a fresh install, release the old activation on the Activations tab first, then refresh the license on the new server. Activations without a check for 30 days are released automatically. See MCP license management.
Not once delivery has started. EU consumers normally have 14 days to withdraw. Licenses for MCP Self-hosted, add-ons and extra seats are delivered as soon as the order is paid, and at checkout you agree to that and confirm that the right of withdrawal ends with it. The right of withdrawal form lists any order that still qualifies. Business orders cannot be withdrawn through the form.
Just MCP Self-hosted plus whichever add-ons you actually need. Tools you haven’t licensed simply aren’t loaded or exposed to your AI client.
Add a Seat from My Account → MCP Self-hosted. Each Seat gets its own token and can be scoped to only the tools that teammate needs.
MCP Self-hosted costs € 217,80 excl. VAT: € 180,00 per year. Add-ons start from € 72,60 excl. VAT: € 60,00 per year and differ in price. Each line on a license, MCP Self-hosted, every add-on and every extra seat, is its own yearly recurring payment through Mollie with its own renewal date. Some products can be billed monthly, with a 12-month minimum term. The pricing calculator adds up a setup for you.
VAT is calculated at checkout from your billing details. A business in the EU with a valid VAT number gets reverse charge, so enter that number at checkout. For a question about the VAT on an existing order, use the contact form and include the order number.
MCP Self-hosted includes 3 seats and 1 activation. One server can serve three people or devices, each with their own token. A fourth identity needs an extra seat at € 18,15 excl. VAT: € 15,00 per year. A second container on the same license is refused until you release the first activation. MCP seats explains tokens, labels and limits.
MCP Self-hosted sends a small diagnostics payload with every license check, so we can see which version runs and whether checks succeed. It contains no data from your tools, inbox, store or database. MCP diagnostics lists exactly what is sent and what you see in My Account.
Nothing breaks immediately. Your server keeps running on its last successful entitlements for a 96-hour grace period before anything is restricted.
A failed charge puts the line on Payment issue and everything keeps working. If it is still unpaid after 7 days, the line is suspended. For the MCP Self-hosted line that blocks every tool call. A cancelled line runs until the end of the period you paid for and then stops. A suspended license gets no 96-hour grace period; that only covers a server that cannot reach AddoCore. Details are in MCP license renewal.
An activation is one running MCP Self-hosted server. A seat is one person or device that connects to it, with its own token, its own tools and its own setting per tool: read-only or Can make changes. One license can have several seats against a single activation. See MCP seats.
Entirely on your own infrastructure — a Docker container you host yourself. Nothing about a tool call routes through a third-party cloud.
Ready to run this for your first client?
Buy MCP Self-hosted, license the tools that client needs, and hand a seat to whoever’s building the integration.