Weissr MCP server
The Weissr MCP server lets AI tools outside Weissr work with your Capex Management data. MCP (Model Context Protocol) is an open standard that AI tools such as Claude use to reach data in other systems. Once an AI tool is connected, you can ask it in plain language to find your requests, show their property values or create a new request. The AI tool always works with your own Weissr login and permissions.
What can an AI tool do through the Weissr MCP server?
The Weissr MCP server offers the same Capex Management capabilities as Weissr Assistant:
Capability | Example question |
|---|---|
Find and filter your requests | "List my open capex requests over 100,000 EUR" |
See property values for a set of requests | "Show site and currency for the requests in category IT" |
Create a new request | "Create a new request for a forklift replacement at Plant 2" |
Which of these are available depends on what your administrator has switched on. The same limits apply as in Weissr Assistant: up to 25 requests per answer by default, up to 100 if you ask, and up to 10 properties per question.
📌 Note: Before a request is created, the AI tool shows you a summary and waits for your confirmation. Read the summary before you confirm, because the request is created in Weissr straight away.
Which AI tools can connect to the Weissr MCP server?
Any AI tool that supports remote MCP servers with OAuth sign-in can connect. OAuth is the standard that lets the AI tool send you to the Weissr login page and then act on your behalf without ever seeing your password.
Claude is tested and documented. See "How do I connect Claude to Weissr?" below.
Other AI tools can connect once your Weissr administrator has allowed them. See "How do I connect another AI tool to Weissr?" below.
🔧 Configuration: The Weissr MCP server works only when your Weissr administrator has switched it on for your installation.
What data can an AI tool see through the Weissr MCP server?
The AI tool acts as you. It can see and do exactly what your Weissr account can, and nothing more. It cannot reach another user's data or get around the restrictions of your role.
Every action is logged. Each call an AI tool makes to Weissr is recorded in the Weissr audit log, with the action, the time and whether it succeeded.
Access is short-lived. The AI tool gets access for 15 minutes at a time and renews it in the background. After 30 days you are asked to log in to Weissr again.
There is a rate limit. Weissr limits how many calls one user can make in a short time. If the AI tool reports a temporary error, wait a moment and try again.
🔒 Data an AI tool reads from Weissr becomes part of your conversation in that tool. The tool's own settings, and your company's agreement with its provider, decide how that conversation is stored.
What do I need before I connect an AI tool?
The address of your Weissr MCP server. It is your Weissr site address followed by
/mcp, for examplehttps://capex.yourcompany.com/mcp.Your normal Weissr login. If your company uses single sign-on for Weissr, it applies here too.
An AI tool and plan that support custom MCP connectors.
How do I connect Claude to Weissr?
You need a Claude plan that supports connectors, such as Pro, Team or Enterprise. On Team and Enterprise plans, your Claude administrator may need to allow custom connectors.
In claude.ai, open Settings and go to Connectors. The exact labels can differ between Claude plans and versions.
Choose Add custom connector.
Enter your Weissr MCP server address, for example
https://capex.yourcompany.com/mcp.Claude opens a Weissr login page. Log in with your Weissr login.
Approve the connection when Weissr asks you to.
The connector shows as connected, and Claude can now use Weissr.
To disconnect, open Settings, go to Connectors, select the Weissr connector and choose Remove or Disconnect. Claude stops using your Weissr access straight away.
How do I connect another AI tool to Weissr?
Check that the AI tool supports remote MCP servers with OAuth sign-in. Its documentation may call this a custom connector, a remote MCP server or an MCP integration.
Ask your Weissr administrator to allow the AI tool. The administrator needs the tool's OAuth redirect address, which you find in the tool's documentation.
In the AI tool, add a remote MCP server with your Weissr MCP server address.
Log in to Weissr when the tool asks you to, and approve the connection.
To disconnect, remove the Weissr connection in the AI tool's settings.
📌 Note: Removing a connection in an AI tool changes nothing in Weissr itself. If you think your access has been misused, also tell your Weissr administrator.
Why does the connection not work?
What you see | What to do |
|---|---|
The AI tool cannot connect | Check that the address uses |
The Weissr login page never opens | Allow pop-ups for the AI tool and try again. If it still does not open, contact your Weissr administrator. |
The login fails with a redirect error | The AI tool is not on the allowed list for your installation. Ask your Weissr administrator to add its redirect address. |
Access denied for one action | Your Weissr role does not allow that action. It works the same way as in Weissr itself. |
Temporary errors when you use it a lot | You have reached the rate limit. Wait a moment and try again. |
The AI tool connects but finds no Weissr tools | Your administrator has not switched on any of the capabilities yet. Ask them to switch on the ones you need. |
How does an administrator set up the Weissr MCP server?
The Weissr MCP server is controlled by application settings for the whole installation.
Setting | What it does |
|---|---|
| Main switch for all AI features. Must be on. |
| Switches on the Weissr MCP server at |
| Lets AI tools register themselves for OAuth sign-in. Must be on for any AI tool to connect. |
| The OAuth redirect addresses of the AI tools that may connect. Add an AI tool's redirect address here to allow it. |
| How long access lasts before it is renewed, 15 minutes by default, and how long before the user must log in again, 30 days by default. |
| Lets AI tools find and filter requests. |
| Lets AI tools show property values for requests. |
| Lets AI tools create requests. |
| Sets how many calls each user can make in a short time. |
The capability settings are the same ones that control Weissr Assistant, so switching one on affects both.
📌 Note: AI tools currently see the server as "Weissr Capex MCP". It will be called "Weissr MCP" from version 5.4.1. Connections that are already set up keep working after the rename.