Connecting Claude or another AI assistant to SynkriaOps

Connecting an assistant means giving it the SynkriaOps MCP server address, then authorising access from your browser. By the end of this page, you will know how to add SynkriaOps to Claude or another MCP client, create a key for an automation without a browser, and check that the connection works.

Prerequisites

• Machine access is open on your account (otherwise, contact SynkriaOps support).
• You have the right to connect an assistant: Administrator, or a colleague they have authorised. By default, no colleague is authorised: see Management decides who uses an AI assistant.
• An assistant able to connect to a remote MCP server (see below).

The server address

https://mcp.synkriaops.com/mcp

It is also shown in SynkriaOps, Settings → AI assistants and MCP, in the Connect your AI assistants block (Copy address button). Enter it exactly, with /mcp at the end.

Two ways to connect

Method	For whom	What happens
Browser connection (recommended)	Claude, or any assistant that can open an authorisation in the browser	No secret to copy. You authorise access on a SynkriaOps page. Valid for 90 days.
Agent key	An automation without a browser (n8n, a script, a service)	You create a secret in SynkriaOps and deploy it yourself, with the expiry of your choice.

The Developer configuration block, at the bottom of the AI assistants and MCP page, sums up the same choice under the heading “When to use which”.

Option 1: browser connection

The connection always starts from the assistant, never from SynkriaOps. When you add the address, the assistant opens your browser on a SynkriaOps authorisation page.

Claude (web and desktop)

1. Copy the address

   In SynkriaOps: Settings → AI assistants and MCP, Copy address button.

2. Add the connector in Claude

   In Claude: Settings → Connectors → Add custom connector. Give it a name (for example “SynkriaOps”) and paste the address.

3. Start the connection

   From the connector’s page, start the connection. Claude opens your browser on app.synkriaops.com. Sign in to SynkriaOps if you are not already signed in.

4. Authorise access

   The Allow Claude to access…? screen appears. Choose the company (or your firm and its client files), the access level, then click Allow N permissions. This screen is described in detail in Authentication and permissions.

5. Return to Claude

   The browser sends you back to Claude. The connector is active and its tools are available in your conversations.

Claude labels

The menu names in step 2 are those of Claude, published by Anthropic. They may change, and adding custom connectors depends on your Claude plan: if in doubt, check Claude’s help.

Claude Code

1. Declare the server

   In a terminal:

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

2. Authenticate

   In a Claude Code session, type /mcp, choose synkriaops and start authentication. Your browser opens on the SynkriaOps authorisation page.

3. Authorise access

   Choose the company or firm, the access level, then Allow N permissions. Back in the terminal, the SynkriaOps tools are available.

Other MCP client

Any assistant that can connect to a remote MCP server with browser authorisation can use SynkriaOps. The SynkriaOps screen mentions Claude, ChatGPT and Cursor. Add the address https://mcp.synkriaops.com/mcp where your client declares a remote MCP server, then follow the authorisation in the browser.

For technical profiles

• Transport: HTTP, a single entry point POST https://mcp.synkriaops.com/mcp, Authorization: Bearer token in the header only.
• Discovery: https://mcp.synkriaops.com/.well-known/oauth-protected-resource/mcp designates the authorisation server https://app.synkriaops.com (metadata at https://app.synkriaops.com/.well-known/oauth-authorization-server).
• OAuth 2.1, “authorization code” flow only, PKCE S256 required, parameter resource=https://mcp.synkriaops.com/mcp.
• The client identifies itself through dynamic registration (RFC 7591) or an https URL used as client_id (client metadata document).
• Accepted redirect addresses: https, or http on localhost, 127.0.0.1 or [::1].
• No refresh token: at expiry (90 days), the client restarts the authorisation.

Option 2: agent key, without a browser

An agent key (or API token) is a secret that replaces browser authorisation. It suits an automation that cannot open a web page (see Automate with n8n for complete examples). It is created in Settings → AI assistants and MCP, Agents and automations section.

1. Open the form

   Click Create an agent.

2. Name the access

   Name field: a name that says what the access is for (for example “n8n reminders”).

3. Choose the use

   Under What will it be used for?, choose API key for a key intended for the MCP server (see the warning below).

4. Choose the permissions

   Under What this access will be able to do, choose a level or tick permissions one by one. You can only grant what you hold yourself.

5. Set an expiry (optional)

   Expiry (optional): Never, 3 months, 6 months, 1 year, 2 years or Custom. Without a date, the key remains valid until it is revoked.

6. Leave the addresses empty

   Allowed addresses (optional) restricts the key to certain network ranges. For use through the MCP server, leave this field empty: calls to SynkriaOps then come from the MCP server, not from your computer.

7. Create the key

   Click Create agent. SynkriaOps asks you to confirm your identity.

8. Copy the secret

   The Write this key down now block shows the key only once. Click Copy key, store it somewhere safe, then I have saved the key, hide it.

AI agent key created before 10 November 2026

Both uses work with the MCP server. A key created by hand with the AI agent use before 10 November 2026 was refused (message MCP token audience is invalid for this resource.): create a new one, then revoke the old one.

Your client is then configured with the address and an authorisation header. The Developer configuration block offers this example:

{
  "mcpServers": {
    "synkriaops": {
      "url": "https://mcp.synkriaops.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

A key is worth your permissions

Never share a key in a code repository, a shared browser or a message. It gives access to your books without a password or two-factor authentication. If it leaks, revoke it immediately.

Checking that the connection works

1. Ask a simple question

   In a new conversation, ask for example: “What is the current fiscal year in SynkriaOps?” or “List my accounting journals”. An accountant connected through a firm can ask: “Which client files can I access?”

2. Check that the assistant called a tool

   Most assistants show when a tool is called (here get_current_fiscal_year, list_journals or list_firm_client_files). The answer must reflect your real data.

3. Check in SynkriaOps

   In Settings → AI assistants and MCP, the access appears under Connected applications (browser connection) or Agents and automations (key), with the used mention and the date of the last call.

Tool names follow your language

The assistant sees the tools in French or English depending on the language of your SynkriaOps profile (or, failing that, the company’s language): get_current_fiscal_year or obtenir_exercice_courant. Both names are accepted.

See also

• Authentication and permissions →
• Assistant capabilities →
• Troubleshoot the connection →