The BLUN MCP Server is coming soon. It is meant to connect BLUN in a controlled way with files, APIs, development tools, and internal systems.
Announced, not yet available.dateien.lesenread onlytickets.vorbereitenallowedrelease.freigebenApprovalThe secure connection between BLUN and your tools.
A model isn’t limited to what a user copies into the chat: it can use functions within clear permissions.
Every system has its own interfaces and access rules. The MCP Server translates them into a unified structure that models and agents understand.
Not every connected system needs full access: tools can be limited to individual actions, projects, or data areas.
The MCP Server is meant to be usable in MCP-compatible development environments and agent systems.
Permissions are set as close to the tool as possible. Not every agent is allowed to perform every action.
When an agent uses a tool, it should remain clear which function was called and which result came back.
Examples of how permissions should look per tool.
Research agent
May read documents, but may not modify them.
Support agent
May access customer data, but may not trigger any payments.
Development agent
May edit files in one project, but not in other workspaces.
QA agent
May start tests and read results, but may not publish anything.
Operations agent
May prepare a process but needs approval to complete it.
Purpose
What task should the tool fulfill?
Features
Which actions are available?
Inputs
What data does each action need?
Permissions
Which roles and projects may access?
tool tickets.vorbereiten
inputtitle, description
permissionsrole: support
result ticket_entwurf
Test
Test with an agent in a real workflow
Operations
Errors, changes, and usage remain traceable
Planned flow. The MCP Server follows.
Collapsed until you need them.
The BLUN MCP Server is meant to be usable in MCP-compatible development environments and agent systems: use BLUN tools in an IDE, give a coding agent controlled project access, provide internal company functions to an agent, let multiple agents work through the same vetted tools, and make your own MCP tools usable through a central connection.
Provide files to a development agent, make internal data accessible to a support agent, offer your own API as a tool, integrate project data into agent workflows, connect document search with BLUN, automate business functions in a controlled way, use the same tools in multiple IDEs.
When BLUN needs to access external data or functions, tools are needed in an IDE or agent runtime, multiple agents should use the same integrations, access rights must be clearly limited, in-house systems should be connected without a custom one-off solution, or tool calls must remain traceable.
The BLUN MCP Server is coming soon. This page describes how it is meant to work.
Four plans: Starter, Pro, Pro Max, and Enterprise. All prices excl. VAT. All four plans are on the central BLUN waitlist. The MCP Server has been announced and is not yet available. The full overview with all features is on the pricing page.
One account for everything in chat.blun.ai: Chat and Work, Sites, Code, images, and voice. Sign up for the right plan or start right away with the BLUN MCP Server.
Learn more