--- title: "Visma Net MCP" description: "This is a guide to get started with the Visma Net MCP." lang: en languages: en: https://docs.vismasoftware.no/vismanetapi/ai/mcp/index.md lastmod: 2026-10-01 --- > Documentation index: https://docs.vismasoftware.no/vismanetapi/ai/llms.txt # Visma Net MCP Last modified October 1, 2026 > This is a guide to get started with the Visma Net MCP. ## Introduction The Visma Net MCP server lets AI assistants running in Model Context Protocol clients — the guide uses Claude as the example client, since it performed best in Visma's own testing — work directly with Visma Net data. Once connected, the assistant can read your data, help with tasks, create data, analyze your data, and present results (tables, dashboards, charts). MCP (Model Context Protocol) is a standard that connects AI agents and language models to the systems they need information from or need to act in. MCP sits on top of the existing Visma Net API: the AI client talks MCP to the MCP server, which in turn calls the API against Visma Net. ![MCP for Visma Net](https://docs.vismasoftware.no/vismanetapi/ai/mcp-diagram.png) > [!TIP] > A good prompt is natural language, but concrete and specific about the details that matter. "Who was my best customer last month?" is hard to interpret ("best" how?); "Which customer had the highest revenue last month?" is easier to answer well. Likewise, disambiguate terms that could mean either side of a relationship (e.g. specify "customer invoice" vs. "supplier invoice" rather than just "invoice"), and prefer wording that maps to actual field names in the system (e.g. say a customer invoice has "passed its due date" rather than just "is overdue," since that maps to the Due date field). ## Endpoint | URL | Description | | --- | ----------- | | | The Visma Net MCP server. | ## Prerequisites: assigning roles in Admin Before connecting a client, correct roles must be assigned in **Admin** (found in Visma Home): 1. Select the relevant user in the left-hand column. 2. Select the relevant company in the middle column. 3. Select either the **AI Connect Read** or **AI Connect Read & Write** role, plus the **API User** role. 4. Click **Grant** for each role, or **Grant all** at the bottom right, to assign the roles. ## Connecting a client ### Claude (claude.ai / Claude apps) 1. Once the Admin roles above are in place, go to **Customize** in the left-hand menu in Claude (this may be collapsed to icons only — expand it if so). 2. Click **Connectors** to see existing connections and to add new ones. 3. Click **+** to create a new connector, then enter a name (e.g. "Visma Net MCP") and the URL: `https://mcp.finance.visma.net/mcp`. 4. Select the new connector in the left-hand menu and click **Connect** in the main panel. 5. A new window opens. If you have the license activated on multiple company databases in Admin, you'll see a list — choose the company database you want Claude to connect to. If you only have access to one company database, you'll skip straight to the next step. 6. Review and accept the permissions Claude is requesting (profile info, email, user identifier, roles, list of organizations; read/write/update access to Visma Net ERP data; offline access). Click **Accept**. > [!TIP] > Creating the connector itself requires admin rights in Claude. If you don't have admin rights, ask your organization's Claude administrator to add the connector for you. ### Enabling individual tools Once Claude has access to the company database, it's worth reviewing tool-level access. From **Customize → Connectors**, select the Visma Net MCP connection, then under both **Interactive tools** and **Read-only tools**, change the permission from **Needs approval** to **Always allow** — otherwise you'll need to confirm and grant access on every use. If these permission options aren't available to you, that indicates you need admin rights to change access on the connector; contact your organization's Claude administrator to have the connector's settings updated. ## Selecting a company You can only be connected to **one company database at a time**. To switch to a different company, disconnect from the current one and reconnect, choosing the other company database during the connect flow described above. ## Read and write access The assistant can be used to: - **Read data** — answer questions about customers, sales, products, accounts, invoices, and so on. - **Create data** — for example, creating a sales order. - **Change data** — for example, updating the status of existing orders. Every prompt that writes to the database will include two things before anything is changed: 1. A presentation of what will be created or changed. 2. A request for confirmation. For example: *"The order looks like this. Should I create it?"* or *"These orders will be changed. Do you want to continue?"* This gives you the chance to review and adjust before confirming — for instance, asking the assistant to "skip order 000024" because it has already been processed and is no longer in a state that should be touched. ## Example usage ### Getting started — simple prompts Good first prompts to test the connection: - "Show me my top 5 customers based on revenue last month" - "Which product did I sell the most of in April?" - "Which customer invoices are more than 30 days past due?" ### More advanced prompts Once comfortable, prompts can go further, including follow-up questions: - "Which product accounted for the largest share of revenue so far this year?" → "What percentage of customers bought this product?" - "Which customers bought two or more unique products in April?" → "What was the average revenue on these?" - "Which products haven't sold in the last six months?" → "Which of these are active stock items?" - "Which customers bought both product 101 and product 301 last year?" → "What do these customers have in common?" - "In which periods was account 1460 over 500,000 last year?" → "Chart the development" ### Creating or changing data - "Create a sales order for customer Demokunde with 1 unit each of product 101, 201 and 301." - "Change the status of all orders for customer Testkunde to On hold." As noted above, expect a preview and a confirmation prompt before anything is written, with the option to exclude specific records (e.g. an order already marked Completed). ### Analyzing data The assistant can also review data, flag things worth checking, and present findings clearly — either from a very specific prompt, or from a general one that lets the assistant decide what to pull. Example: *"Can you go through the 2025 accounts and see if you find any anomalies?"* The assistant can surface flagged items (e.g. an unusually large unpaid supplier invoice, or an account with a long-standing negative balance) grouped by risk, alongside supporting figures (invoice/account reference, amount, date), and let you drill into any one of them for a follow-up analysis. Results can also be turned into a PowerPoint presentation for sharing with others. ### Dashboards The assistant can also build a dashboard, e.g. from a prompt like *"Build a dashboard with the company's key financial figures,"* combining summary metrics (revenue, receivables, payables, open orders), a revenue-by-month chart, and a revenue-by-customer breakdown. ### On mobile These same commands can be run from a phone — MCP client providers (like Claude) typically have their own mobile apps for this, so you can, for example, look up information on the way to a customer visit and create a quote on the way home. ## Safety and constraints - **Creating the connector** — a Claude administrator must add the Visma Net MCP server as a connector before it becomes visible to a regular user. - **One company database at a time** — connecting to a different company requires disconnecting from the current one and reconnecting. - **Only Admin roles are honored** — only the AI Connect Read / Read & Write roles (plus API User) assigned in Admin govern MCP access; other restrictions configured under access control inside Visma Net are not taken into account by the MCP connection. - **Feedback stays local to the client** — a thumbs up/down inside Claude is feedback to Claude only, not to Visma. ## Support To help Visma support investigate an issue efficiently, include: - **The prompt** — the exact prompt you entered in Claude, and what result you expected. - **An .md file** — for troubleshooting, ask the assistant directly: *"Please give me all the queries, changes and flow in an .md file for further troubleshooting."* - **API calls** — if any API calls appear in the dialogue between the assistant and the MCP server, include those too. - **A screenshot** — from Claude, showing the prompt and what happened next. - **Confirmation you've tried it manually** — there's an expectation that you've attempted the equivalent task directly in the Visma Net interface, with equivalent access, as far as that's practical, before raising a support case. ## Webinar Visma ran a [webinar](https://www.vismalearninguniverse.com/share/asset/view/1118) for partners ahead of launch, covering what MCP is, activating MCP against Visma Net, and live prompting examples with results from earlier testing. --- [View this page](https://docs.vismasoftware.no/vismanetapi/ai/mcp/)