Nordsynk — Fortnox MCP

se.nordsynkPublished by nordsynk.seOfficial publisherv1.0.0Updated Oct 24, 2026

Hosted MCP server for Fortnox. Connect Claude, ChatGPT, Cursor to live Fortnox via OAuth.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A hosted MCP server that connects AI assistants to a live Fortnox account through OAuth.

What you can do
Connects an assistant to a live Fortnox account over a hosted remote endpoint, with OAuth sign-in rather than API keys or local setup. Intended for assistants such as Claude, ChatGPT and Cursor, so accounting data can be reached from within those clients. The published listing does not name individual tools, so the exact actions available are not documented here.
When to use it
Useful when you want an AI assistant to work with your Fortnox accounting data without building or hosting your own integration, and you are comfortable authorizing access through OAuth.
Requirements
A remote MCP endpoint at mcp.nordsynk.se reached over streamable HTTP, plus a Fortnox account and an OAuth authorization flow. No packages, environment variables or headers are declared.
Before you install
OAuth grants the server access to your Fortnox account, so review the scopes and permissions requested during authorization. The listing does not document which tools exist or whether they can create, change or delete accounting records; confirm this before connecting a production account. Data is handled by a third-party provider, Nordsynk.

Installation

In SourceWeft

  1. Open Nordsynk — Fortnox MCP 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.nordsynk%2Ffortnox/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": {
    "nordsynk-fortnox": {
      "type": "http",
      "url": "https://mcp.nordsynk.se/"
    }
  }
}

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. v1.0.0LatestSep 16, 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.