Novus för byråer: Fortnox for accounting firms

se.novusmcpPublished by novusmcp.seOfficial publisherv0.1.0Updated Oct 25, 2026

Fortnox for accounting firms: every client company in one connection. Read-only per company.

The publisher's own server: Novus: Fortnox in your AI assistant

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant read-only access to Fortnox data for every client company an accounting firm manages, in one connection.

What you can do
Connect an assistant to Fortnox data across all client companies of an accounting firm through a single connection, with access scoped per company and read-only. The manifest lists no individual tools, so the exact operations are not documented here. It is a hosted remote endpoint rather than a local package.
When to use it
Useful for accounting firms that want an AI assistant to look up Fortnox information for multiple client companies without setting up a separate connection per client.
Requirements
A remote streamable HTTP endpoint; no local runtime or package is needed. OAuth authentication is required, and the assistant must be able to complete that sign-in. No environment variables or headers are declared.
Before you install
Access covers client companies' accounting data, so confirm which companies the OAuth account exposes and that access is read-only before relying on it. The provider is a third party, so client financial data passes through its service.

Installation

In SourceWeft

  1. Open Novus för byråer: Fortnox for accounting firms in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/se.novusmcp%2Fnovus-byra/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "novus-f-r-byr-er-fortnox-for-accounting": {
      "type": "http",
      "url": "https://byra.novusmcp.se/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 22, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Novusmcp integrations