MCP.so
Sign In

Nextesy MCP ServerVerifiedFeatured

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Productivity

Submitted by

Gerrit Kesten

About Nextesy MCP Server

Nextesy MCP is a remote MCP server for clients who use nextesy software. Available at https://nextesy-mcp.com. Not an official app by nextesy.

#nextesy#ai

Connection details

https://nextesy-mcp.com/mcp

Setup

claude mcp add nextesy-mcp --transport http https://nextesy-mcp.com/mcp

Nextesy MCP Server tools

161

Reopen a READY payroll employee row (UI: 'Als in Bearbeitung markieren') so wages can be edited.

Read and flatten the live chart hierarchy for a group-number preflight.

Read account records including parentGroupNumber/type/flags for preflight.

Preflight then create one chart account; dry-run is default and sends no POST. `parentGroupNumber` is a live-discovery guard and intentionally is not sent: the verified CreateAccountRequest does not include a group-id field.

Read cost centers. The API supports only the verified `search` filter.

Read expense/accounting rules, including their costCenterId assignment.

Create a non-auto-booking accounting rule; costCenterId is the verified assignment field.

Read-merge-validate a PUT request so unedited live fields are retained.

Read bank transaction rules, including costCenterId and current automation state.

Separate activation control. Never called by create/edit; must be explicit.

Explicitly enable automatic booking; this is deliberately separate from rule CRUD.

The verified API exposes AI processing state in the company resource; no separate GET exists.

List the selected company's document store, one-based pages; no file contents inferred.

Read metadata for an exact document in the selected company.

Search all 768 historical API operations; discovery is NOT implementation/current UI completeness.

Exact parameters/body from pinned historical provider contract, plus actual reader restrictions.

Fixed allowlisted JSON GET only. No URLs/headers/tenant overrides, binary downloads or writes. Query beans are FLAT.

NON-EXECUTING historical JSON-schema preview; no finance/send action, business preflight or human consent is established.

Fixed JSON GET /api/v1/sales/purchases. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/purchases/{purchaseId}. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/purchases/{purchaseId}/payments. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/purchases/{purchaseId}/settlements. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/reports/balance-sheet. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: dateTo.

Fixed JSON GET /api/v1/reports/profit-and-loss. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: dateFrom, dateTo.

Fixed JSON GET /api/v1/reports/account-balance. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: dateFrom, dateTo, accountNumber.

Fixed JSON GET /api/v1/reports/cost-centers. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: dateFrom, dateTo.

Fixed JSON GET /api/v1/reports/vat. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: period, year.

Fixed JSON GET /api/v1/accounting/fiscal-years. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/fiscal-years/{id}. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/fiscal-years/closing/state. Explicit company required. Flat query fields; see describe_nextesy_operation for filters. Required query fields: fiscalYearId.

Fixed JSON GET /api/v1/accounting/journal/entries. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/journal/account-statement-entries. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/subledgers/customer/entries. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/subledgers/supplier/entries. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/booking-templates. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/booking-templates/{id}. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/accounting/bookings/recurring-series. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/documents/folders. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/documents/{id}/email-history. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/document/preferences. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/banking/preferences. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/orders. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/orders/{orderId}. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/credit-notes. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/credit-notes/{creditNoteId}. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/contacts/{contactId}/overview. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/contacts/{contactId}/sales-overview. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/configuration. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/company. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/policies. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/periods. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/company/working-time-models. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/payroll/wage-types. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/company/workplaces. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Fixed JSON GET /api/v1/sales/labels. Explicit company required. Flat query fields; see describe_nextesy_operation for filters.

Explain current captured AI rule fields, create/edit semantics and verification limits.

Read current document or bank/card AI rules. all_pages reconciles IDs/totals or fails.

Read a rule and its mutable-field revision for a drift-checked edit.

Create an AI rule without enabling automatic booking. Default: real masterdata GETs and payload preview, no write. Live creation requires existing business approval.

Read/merge/edit a rule without losing its cost center or other unedited fields. Default preview; preserves existing automation but never enables it.

Clone within the same exact company, retaining assignments but forcing automatic booking off. Default preview.

Preflight up to 100 create/edit operations, with exact scope/masterdata and diffs. This tool can NEVER execute the batch.

Completely scan both rule families, reconcile totals, flag broad conditions, incomplete rules, exact duplicates and unbounded auto-booking. Never changes a rule.

Read the two AI rule-creation preferences, explicitly distinct from automatic financial booking.

Read the durable exact-company receipt/status of a rule write. Never retries it.

Reconcile an uncertain rule write by real exact-company GETs only. No POST/PUT/PATCH/DELETE is retried. A create without a returned ID stays explicitly uncertain.

Delete one exact AI rule only on an explicit user business instruction. Default preview; durable no-retry intent and exact post-readback. Never deletes a financial booking.

Set automatic AI RULE CREATION (not automatic bookkeeping) for documents or bank/cards. Default preview; requires an explicit user instruction for live use.

Separate FINANCIALLY SIGNIFICANT auto-booking control. Never invoke without the user's matching approval. Default preview; enabling requires explicit_enable and does not authorize a test booking.

Overview

Website: https://nextesy-mcp.com
Provider: 3agenteers / Chestnut Innovation GmbH
Business Model: SaaS with Free and Pro plans

What is Nextesy MCP?

Nextesy MCP connects Nextesy, a Swiss business management and accounting platform, with AI assistants such as ChatGPT, Claude, Gemini, and other MCP-compatible clients.

Using the Model Context Protocol (MCP), AI assistants can securely access business data stored in Nextesy and, with the Pro version, execute authorized actions.

This allows businesses to manage accounting, invoicing, and administrative tasks using natural language instead of manually navigating the Nextesy interface.

Features

Free – Read Access (CHF 0)

AI assistants can retrieve, analyze, and summarize existing Nextesy data.

Example use cases:

  • Retrieve outstanding and overdue invoices
  • Look up customers and contacts
  • Review invoice amounts and payment deadlines
  • Summarize business and accounting information

The Free version provides read-only access.

Pro – Execute Actions (CHF 19/month)

In addition to read access, AI assistants can execute supported write operations in Nextesy.

Example use cases:

  • Create quotations from customer conversations
  • Prepare customer invoices from timesheets
  • Create invoices and quotations after approval
  • Automate administrative workflows with AI agents

Available actions depend on supported functionality and granted permissions.

Supported AI Assistants

Nextesy MCP is designed to work with MCP-compatible applications, including:

  • ChatGPT
  • Claude
  • Claude Code
  • Cursor
  • OpenAI Codex
  • Gemini CLI
  • Hermes Agent

Other MCP-compatible clients may also be supported through appropriate configuration.

Pricing

FeatureFreePro
PriceCHF 0CHF 19/month
Read business dataYesYes
Execute write actionsNoYes
BillingPer companyPer company
Self-hosting requiredNoNo

Prices exclude VAT. A Nextesy account and any applicable AI provider subscriptions are required separately.

Technical Architecture

  • Protocol: Model Context Protocol (MCP)
  • Deployment: Hosted remote MCP server
  • Endpoint: https://nextesy-mcp.com/mcp
  • Authentication: OAuth or personal HTTP credentials, depending on the client
  • Access control: Company-specific permissions and existing Nextesy access rights
  • Hosting: Fully hosted, no infrastructure setup required
  • Security: Encrypted session tokens, revocable access, and separate write permissions

Target Audience

Nextesy MCP is designed for Swiss SMEs, freelancers, accountants, and teams using Nextesy who want to simplify or automate business operations with AI.

It is particularly useful for organizations handling recurring accounting, invoicing, customer management, and administrative workflows.

Current Status

Nextesy MCP is an independently developed integration and is not an official Nextesy product.

The service is currently available as a public synthetic preview. Real changes to Nextesy data and payments are disabled in this preview environment.

Product Positioning

Nextesy MCP makes Nextesy accessible to AI agents.

Rather than creating another accounting interface, the product provides a standardized bridge between existing business software and modern AI assistants.

The commercial value lies primarily in the Pro version: businesses pay to enable their AI assistants not only to retrieve information but also to execute authorized business operations.

Website: https://nextesy-mcp.com

Frequently asked questions

1

What is the Nextesy MCP remote MCP server?

The Nextesy MCP remote MCP server is a hosted Model Context Protocol endpoint at https://nextesy-mcp.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Nextesy MCP MCP server?

Add the endpoint https://nextesy-mcp.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Nextesy MCP MCP server require authentication?

Yes. Nextesy MCP uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Nextesy MCP MCP server use?

Nextesy MCP exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments