Zusammenfassung
Sellsy: Französisches CRM und Rechnungsstellung: Unternehmen, Kontakte, Verkaufschancen, Rechnungen, Angebote, Artikel und Zahlungen. REST API v2, OAuth 2.0 Client Credentials.
Geführte Einrichtung
Sellsy in 2 Minuten mit Microsoft Copilot verbinden
Starte die kostenlose Testphase in der AnythingMCP Cloud, verbinde Sellsy in der geführten Einrichtung und trag deine MCP-URL in Microsoft Copilot ein. Ohne Code, ohne eigenen Server.
Keine Kreditkarte · 7 Tage Test · Self-Hosting-Alternative verfügbar
Frag einfach
Beispiel-Prompts für Sellsy
Klick auf einen Prompt, um ihn zu kopieren. In Claude, ChatGPT, Cursor, Gemini, Copilot oder OpenClaw einfügen — und gegen diesen Connector laufen lassen.
Claude ist KI und kann Fehler machen. Bitte Antworten gegenprüfen.
💡 Keine Installation? Nutze cloud.anythingmcp.com direkt. Einloggen, Connectors → Sellsy klicken, Zugangsdaten einfügen, MCP-API-Key erzeugen — fertig. Kein Docker, kein
git clone, kein lokaler Server.
Sellsy + Microsoft Copilot
Sellsy: Französisches CRM und Rechnungsstellung: Unternehmen, Kontakte, Verkaufschancen, Rechnungen, Angebote, Artikel und Zahlungen. REST API v2, OAuth 2.0 Client Credentials.
Voraussetzungen
Die vollständige Setup-Anleitung ist in den Connector eingebaut (im Store sichtbar, wenn du den Connector auswählst). Benötigte Umgebungsvariablen für diesen Connector:
SELLSY_CLIENT_ID, SELLSY_CLIENT_SECRET
Schritt 1 — Zugangsdaten holen
Getting credentials
- Sign in to Sellsy, open Paramètres → API and create an application in the developer area.
- Choose the client credentials flow — it authorises the application against your own account with no browser consent step. You receive a client id and client secret.
- Set
SELLSY_CLIENT_IDandSELLSY_CLIENT_SECRET. AnythingMCP mints and refreshes the access token on its own.
This is API v2, at https://api.sellsy.com/v2. Sellsy's v1 was an entirely different, single-endpoint RPC API — if you find an example that POSTs everything to one URL with a request parameter, that is v1 and it does not apply here.
…(continued in the in-app connector instructions)
Schritt 2 — Adapter installieren
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Schritt 3 — Connector in Microsoft Copilot hinzufügen
Deine Server-URL: Öffne in AnythingMCP MCP Servers → den Server, auf dem dieser Connector liegt, und kopiere seine URL (
https://cloud.anythingmcp.com/mcp/…). Setze sie überall ein, wo diese AnleitungYOUR_SERVER_IDzeigt.
Microsoft Copilot nutzt MCP-Server über Agents, die du in Copilot Studio baust: Du fügst AnythingMCP einem Agent als Tool hinzu und veröffentlichst den Agent dann in Microsoft 365 Copilot und Teams. Copilot Studio verbindet sich aus der Cloud von Microsoft per Streamable HTTP, das AnythingMCP unterstützt.
- Öffne in Copilot Studio deinen Agent (oder leg einen an), geh zu Tools und wähle Add a tool → New tool → Model Context Protocol.
- Trag einen Server name ein (zum Beispiel
AnythingMCP), eine Server description, die sagt, was der Connector kann, und die Server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Anhand der Beschreibung entscheidet Copilot Studio, wann es den Server aufruft. - Wähle bei der Authentifizierung API key, setze Type auf Header und den Header-Namen auf
X-API-Keyund klicke auf Create. - Wähle in Add tool die Option Create a new connection, füge einen MCP-API-Key aus AnythingMCP ein (MCP Servers → dein Server → API keys) und klicke auf Add to agent.
- Probier es im Test-Bereich des Agents aus: Bitte um etwas, wofür er die
Sellsy-Tools braucht. - Klicke auf Publish, dann auf Channels → Microsoft 365 and Microsoft Teams, lass Make agent available in Microsoft Copilot aktiviert und wähle Add channel. See agent in Teams installiert den Agent für dich; in Microsoft 365 Copilot tippst du @ und wählst den Agent aus.
Lieber eine Anmeldung pro Person? Wähle statt API key OAuth 2.0 → Dynamic discovery: Dann meldet sich jede Person beim ersten Aufruf des Agents bei AnythingMCP an.
Du hostest selbst? Nimm statt https://cloud.anythingmcp.com die öffentliche HTTPS-Adresse deiner Instanz. Copilot Studio verbindet sich aus der Cloud von Microsoft, localhost funktioniert deshalb nicht.
Verfügbare Tools
| Tool | What it does |
|---|---|
sellsy_list_companies | List client companies with their name, SIRET, VAT number, address and owner |
sellsy_search_companies | Search companies with Sellsy's filter object — far more expressive than the plain list |
sellsy_get_company | Read one client company in full: addresses, contacts, tax identifiers, rating and the notes recorded against it |
sellsy_list_contacts | List individual contacts with their name, e-mail, phone, position and the company they belong to |
sellsy_list_invoices | List invoices with their number, date, due date, client, net and gross totals and payment status — the receivables view |
sellsy_search_invoices | Search invoices with Sellsy's filter object — by status, date range, client or amount |
sellsy_get_invoice | Read one invoice in full: every row with its quantity, unit price, discount and VAT, the totals and the payments applied against it |
sellsy_list_estimates | List estimates (devis) with their number, date, client, total and acceptance status — what is out with prospects and not yet won |
sellsy_list_opportunities | List CRM opportunities with their name, client, amount, funnel step and expected close date — the pipeline view |
sellsy_list_items | List catalogue items with their reference, name, unit price, VAT rate and stock tracking flag |
sellsy_get_contact | Read one contact (person) in full: name, email and phone numbers, position, note, addresses, owner, archive state and custom fields |
sellsy_list_contact_companies | List the companies a contact is linked to |
sellsy_edit_contact | Change fields of a contact |
sellsy_edit_company | Change fields of a company |
sellsy_create_company | Create a company (a client, prospect or supplier) |
sellsy_list_company_contacts | List the contacts (people) linked to a company, with name, e-mail, phones, position and their roles at the company |
sellsy_link_contact_to_company | Link an existing contact to a company, optionally with roles (e.g. ["main", "invoicing", "dunning"]) |
sellsy_list_company_addresses | List the addresses of a company (invoicing, delivery and others) with their ids, for use as invoicing_address_id or delivery_address_id on… |
sellsy_create_company_address | Add an address to a company |
sellsy_get_company_custom_fields | Read the custom field values of a company: field id, name, type and value |
sellsy_update_company_custom_fields | Set custom field values on a company |
sellsy_list_company_files | List the directories and files attached to a company (contracts, scans, exports), with file ids for sellsy_get_file |
sellsy_list_individuals | List individuals (private persons who are clients, prospects or suppliers in their own right, unlike contacts who belong to a company) with… |
sellsy_search_individuals | Search individual with Sellsy's filter object (a POST that only reads) |
sellsy_get_individual | Read one individual in full: name, contact details, type, addresses, owner and notes |
sellsy_create_individual | Create an individual (a private person as client, prospect or supplier) |
sellsy_edit_individual | Change fields of an individual |
sellsy_search_contacts | Search contact with Sellsy's filter object (a POST that only reads) |
sellsy_create_contact | Create a contact (a person, usually working at a company) |
sellsy_get_opportunity | Read one opportunity: name, status, pipeline and step, amount, probability, due date, source, related company or individual, contacts… |
sellsy_search_opportunities | Search opportunity with Sellsy's filter object (a POST that only reads) |
sellsy_create_opportunity | Create an opportunity in a pipeline step for a company or individual |
sellsy_update_opportunity | Partly update an opportunity, e.g. mark it won or lost, change its amount or due date |
sellsy_move_opportunity_step | Move an opportunity to another step of its pipeline (the kanban move), optionally placing it before another opportunity |
sellsy_list_opportunity_pipelines | List the opportunity pipelines (sales funnels) with their ids and names |
sellsy_list_pipeline_steps | List the steps of one pipeline in order, with id, name, rank and default probability. embed opportunities_number adds how many… |
sellsy_list_opportunity_sources | List the opportunity sources (where leads come from: website, trade fair, referral...) with their ids |
sellsy_list_opportunity_categories | List the categories that group opportunity sources; embed sources returns the sources of each category |
sellsy_get_estimate | Read one estimate (devis) in full: number, date, expiry date, status, related parties, rows with quantity, price and VAT, totals and the… |
sellsy_search_estimates | Search estimate with Sellsy's filter object (a POST that only reads) |
sellsy_create_estimate | Create an estimate (devis) as a draft |
sellsy_update_estimate_status | Change the status of an estimate, e.g. to accepted when the client signed or refused when they declined |
sellsy_create_invoice | Create an invoice as a draft (it gets its final number when validated with sellsy_validate_invoice) |
sellsy_validate_invoice | Validate a draft invoice: it gets its definitive number, can no longer be edited and is due |
sellsy_list_invoice_payments | List the payments recorded on one invoice: amount, date, payment method and status |
sellsy_list_invoice_credit_notes | List the credit notes linked to one invoice (refunds and corrections), with number and amounts |
sellsy_list_invoice_files | List the directories and files attached to one invoice, with file ids for sellsy_get_file |
sellsy_list_credit_notes | List credit notes (avoirs) with number, date, client, amounts and status (draft, stored, partialspend, spent, cancelled) |
sellsy_search_credit_notes | Search credit note with Sellsy's filter object (a POST that only reads) |
sellsy_get_credit_note | Read one credit note in full: rows, totals, status, related parties and the invoices it refers to |
sellsy_list_orders | List sales orders (bons de commande) with number, date, client, amount, status and delivery status (order_status: none, wait, picking… |
sellsy_search_orders | Search order with Sellsy's filter object (a POST that only reads) |
sellsy_get_order | Read one sales order in full: rows, totals, status, delivery status and related parties |
sellsy_list_deliveries | List delivery notes (bons de livraison) with number, date, client and delivery status |
sellsy_list_payments | List payments received or made, with amount, currency, paid date, payment method, status and the documents they settle |
sellsy_search_payments | Search payment with Sellsy's filter object (a POST that only reads) |
sellsy_get_payment | Read one payment: amount, date, method, status, number and the documents it is allocated to |
sellsy_list_payment_methods | List the payment methods of the account (transfer, card, cheque, direct debit...) with their ids for payment_method_ids on documents |
sellsy_get_item | Read one catalogue item: type, reference, name, description, reference price, purchase price, VAT, unit and accounting codes |
sellsy_search_items | Search item with Sellsy's filter object (a POST that only reads) |
sellsy_create_item | Create a catalogue item (product or service) |
sellsy_edit_item | Change fields of a catalogue item |
sellsy_get_item_prices | Read the prices of an item per rate category (price lists), with amounts with and without tax |
sellsy_list_taxes | List the VAT rates (taxes) of the account with id, rate and label, for tax_id on items and document rows |
sellsy_list_units | List the units of measure (piece, hour, day, kg...) with their ids, for unit_id on items and rows |
sellsy_list_currencies | List the currencies available on the account, with code and symbol |
sellsy_list_payment_terms | List the payment terms of the account (on order, 30 days, end of month...) with their ids, for payment_terms on invoices and estimates |
sellsy_list_rate_categories | List the rate categories (price lists such as retail or wholesale) with their ids |
sellsy_list_custom_fields | List the custom field definitions of the account: id, name, code, type, options and which objects they apply to |
sellsy_list_tasks | List tasks (to-dos) with title, due date, status (todo or done), label, priority, assignees and the record they belong to |
sellsy_search_tasks | Search task with Sellsy's filter object (a POST that only reads) |
sellsy_get_task | Read one task: title, description, due date, status, label, priority, reminders, assignees and the related record |
sellsy_create_task | Create a task (to-do) on a record, e.g. a follow-up call on a company |
sellsy_update_task | Update a task, e.g. set status done, move the due date or reassign it |
sellsy_list_task_labels | List the task labels (types such as call, e-mail, meeting) with their ids, for label_id when creating tasks |
sellsy_list_comments | List comments (notes left on companies, contacts, opportunities and documents) with text, author, date and related record |
sellsy_search_comments | Search comment with Sellsy's filter object (a POST that only reads) |
sellsy_create_comment | Add a comment (note) to a record, e.g. a summary of a call on a company or opportunity |
sellsy_list_calendar_events | List calendar events (meetings, appointments) with title, start and end, label, participants and related record |
sellsy_search_calendar_events | Search calendar event with Sellsy's filter object (a POST that only reads) |
sellsy_get_calendar_event | Read one calendar event: title, description, start and end, all-day flag, label, participants and related record |
sellsy_create_calendar_event | Create a calendar event (meeting or appointment), optionally linked to a record and with participants |
sellsy_update_calendar_event | Update a calendar event, e.g. move it or change its title |
sellsy_list_calendar_event_labels | List the calendar event labels (meeting, call, demo...) with their ids, for label_id when creating events |
sellsy_list_crm_activity | Read the CRM activity feed: e-mails, calls, meetings, comments and other events logged on records, with date, author and label |
sellsy_list_staffs | List the staff members (users of the Sellsy account) with id, name, e-mail and status |
sellsy_get_staff | Read one staff member |
sellsy_list_teams | List the teams of the Sellsy account (groups of staff members) with their ids and members |
sellsy_get_file | Read one file attached in Sellsy: name, size, type, the record it belongs to and its download link |
sellsy_list_subscriptions | List subscriptions (recurring invoicing plans) with client, frequency, amounts and next invoice date |
sellsy_get_subscription | Read one subscription (recurring invoicing plan); embed payment_installments adds its installments |
sellsy_search | Search the whole account by text, like the search bar: companies, individuals, contacts, opportunities, items, documents and staff |
sellsy_get_quotas | Read the API quotas of the account: requests allowed and used in the current windows |
FAQ
Für welchen Copilot gilt das? Für Microsoft 365 Copilot im Unternehmen, über Agents aus Copilot Studio. Die Microsoft-Copilot-App für private Konten bietet keine Möglichkeit, einen eigenen MCP-Server hinzuzufügen.
Was brauche ich? Ein Arbeitskonto mit Zugang zu Copilot Studio (Lizenz oder Testversion), um den Agent zu bauen. Wer ihn in Microsoft 365 Copilot oder Teams nutzen soll, braucht Zugriff auf den Agent: Teile ihn oder lass ihn von einem Admin für die Organisation veröffentlichen. Wendet deine Organisation Datenrichtlinien auf Power-Platform-Connectors an, gelten sie auch für MCP-Server.
Der Agent ruft die Tools nicht auf. Prüfe, dass der Header-Name genau X-API-Key lautet und der Schlüssel zum selben MCP-Server gehört wie die URL, und formuliere die Server description konkret: Copilot Studio entscheidet anhand der Beschreibung, wann es den Server aufruft. Veröffentliche den Agent nach jeder Änderung erneut; in einem offenen Chat holst du die neue Version mit „start over“.
Nächste Schritte
- Connector-Startseite
- Mit Claude verbinden
- Mit ChatGPT verbinden
- Mit Cursor verbinden
- Mit Gemini verbinden
- Mit Meta Muse verbinden
War dieser Guide hilfreich?
