Skip to content

MCP Servers

Connect AI agents to your systems under control – with sign-in, clear permissions and traceable access.

dectria builds MCP servers through which AI applications such as Claude, ChatGPT, Microsoft Copilot Studio or your own agents access your systems: reading data, finding documents, creating records. Every access runs through defined tools, with sign-in and the permissions of the respective user.

We run MCP in production ourselves: via MCP, Claude or your own agents can connect securely to NetCero, an ESG platform in which dectria holds a stake. Access is secured with OAuth and role-based permissions.

We start with a few narrowly scoped tools and only expand once it is clear how agents actually use them.

Official website Michael Jauk Your contact Michael Jauk Contact for AI & data

What is MCP – and when is it worth it?

The Model Context Protocol (MCP) is an open standard through which AI applications access external data and functions. An MCP server provides tools, resources and prompts that any MCP-capable AI application can use without its own integration.

MCP is worth it when several AI applications or agents need to access the same systems, or when users want to work with company data directly in their AI assistant. It is not worth it when a fixed process should always run the same way – a classic interface is more predictable there. And if agents would write to critical systems, you first need human approval, not more tools.

MCP or classic API integration?

MCP serverClassic API integration
Who decides on the callthe model, based on the tool descriptionhard-coded logic
Connecting a new AI applicationno extra effort if it supports MCPseparate integration per application
SecurityOAuth 2.1, permissions per toolAPI keys or OAuth, depending on the system
Predictabilitylower – approval needed for critical stepshigh
Suited forassistants and agents with open-ended tasksfixed, recurring processes

Capabilities

What We Build with MCP

MCP Server Development (TypeScript) OAuth 2.1 & Protected Resource Metadata Integration with Existing Identity Providers Permissions per Tool (RBAC) Tool Design & Descriptions MCP for Legacy Systems Without Connectors Approval Workflows (Human-in-the-Loop) Logging & Traceability Code Mode & Sandbox Execution Testing with Common AI Clients Operation in the EU

Use Cases

Typical Use Cases

AI Access to Company Data

Employees ask their AI assistant about customers, orders or documents – the MCP server returns only what that person may see.

Agents for Recurring Tasks

Agents create tickets, prepare reports or reconcile data; critical steps go to a person for approval first.

Making Legacy Systems AI-Ready

For systems without a ready-made connector, the MCP server becomes the adapter – with narrowly scoped tools instead of direct database access.

References

Selected Projects

Klanglicht Audio Guide
Web Application

Klanglicht - Art Festival of Bühnen Graz

Klanglicht Audio Guide
Soundportal App
Mobile App

Radio Soundportal

Soundportal App
Deposit Insurance Payout Platform
Web Application

Österreichische Raiffeisen-Sicherungseinrichtung eGen (ÖRS)

Deposit Insurance Payout Platform
View all references

FAQ

MCP FAQ

What is an MCP server?
A service that provides an AI application with defined tools and data through the Model Context Protocol. The AI only sees what the server offers and calls functions only through these tools. This keeps access to your systems limited and traceable.
How is an MCP server secured?
With OAuth 2.1: the MCP server checks every access token and only accepts tokens issued for it. We grant permissions per tool and follow the principle of least privilege; sign-in runs through your existing identity provider, such as Microsoft Entra ID. Write actions can require human confirmation.
Which AI applications support MCP?
MCP is an open standard. Claude, ChatGPT and Microsoft Copilot Studio can connect custom MCP servers, as can the agent tooling from Anthropic, OpenAI, Microsoft and Google. An MCP server therefore works with several AI applications and your own agents, without an integration per application.
Does MCP work for legacy systems without an API?
Yes. The MCP server then becomes the adapter: it reads from existing interfaces, databases or files and gives agents only narrowly scoped tools, no direct database access. This way, even systems without a ready-made connector can be connected.
What is Code Mode in MCP?
Code Mode is a pattern in which the model does not call MCP tools one by one but writes short code against a TypeScript interface generated from them. The code runs in an isolated sandbox, and only the result goes back to the model. With many tools and multi-step tasks, this saves a lot of context and cost. With few tools and simple queries, direct calls are simpler – we decide based on the scope of the MCP server.

Every project starts with a conversation.

Let us talk about your individual needs and goals.

Start a project