AI Impact Stack · MCP servers

Agents with access to ERP and shop, on your terms

From answering to acting.

Many pilots can answer, but cannot book, order or approve. An agent gateway in your infrastructure gives agents access to ERP, shop and internal services via MCP servers, with clear permissions, logging and approvals.

Agent gateway

Controlled access to your systems

Every agent gets exactly the permissions its task requires.

An MCP server describes to agents what a system can do: create an order, query stock, check a price, change master data. MCP (Model Context Protocol) is the open standard through which agents use such tools.

The agent gateway bundles these servers, orchestrates microservices and internal systems, and enforces your rules. Every step is logged. Where you specify it, the agent proposes and a person approves. Your existing systems stay as they are; via APIs and MCP servers, they become accessible to agents.

  • Permissions per agentRead, book or approve, defined per task and system
  • LoggingEvery access and every action is traceable
  • ApprovalsThe agent acts on its own or proposes, exactly as you specify
  • Data sovereigntyGateway and data stay in your infrastructure

What the gateway delivers

From pilot to process

Only with access to your systems does an agent work within the process. This is level one in the maturity model: systems and data are accessible, agents can read and book.

  • Agents act within the process.

    Capturing orders, querying stock, maintaining master data, directly in ERP and shop and within your rules.

    Result: lower cost per transaction.

  • One access point for many agents.

    Built once, service, sales and management agents use the same MCP servers with the same rules.

    Result: every additional agent launches faster.

  • Control you can audit.

    Permissions, logging and approvals are managed centrally and visible to IT, data protection and business teams.

    Result: agents go into regular operations with the consent of everyone involved.

From foobar Labs into your project.

We keep developing MCP server building blocks in foobar Labs. What comes out of that goes into our tools and from there into your project.

Technology partners

Connected to the platforms you run

The gateway runs wherever it fits your architecture, for example on Vercel or in your own cloud on AWS, Azure or Google, and connects commerce, data and content.

  • Logo von commercetools
  • Snowflake Logo
  • Logo von Contentful
  • Logo von Algolia

FAQ

What CIOs ask before the first system access

An interface based on the open Model Context Protocol. It describes to agents which data and functions a system provides, such as "create order" or "query stock", and how they are called.

The ones the first agent needs for its process, usually ERP, shop or PIM. Access grows with every further agent. Once an MCP server is in place, all following agents use it too.

We do, as long as we are responsible for operations, and your team afterwards. The servers are documented, and changes to a system are made in one place and apply to all agents.

In your infrastructure, for example in your cloud on AWS, Azure or Google, or on Vercel. The choice depends on your architecture and your security requirements.

Your own agents as well as agents running in platforms such as Snowflake, Databricks or n8n. All of them access it under the same rules.

Getting started

In two weeks, you know which systems your agent needs

The Impact Check examines system access as one of the four hurdles and outlines in the blueprint which MCP servers your first agent will work through.

Get in touch

We look forward to your enquiry.

Please accept marketing cookies to load the registration form.