Connect Sirenic to your assistant
Our 77 tools covering French and European company data plug into an assistant by pasting a single URL. Your assistant then queries the official registers itself, without you leaving the conversation.
The URL to paste
https://api.sirenic.eu/mcp/connecteur
Remote MCP server, streamable HTTP transport. The same address for every client below.
Two ways to authenticate
1. OAuth
- The client opens a Sirenic window: you sign in, you authorise, and that is it.
- Nothing to type in: no client ID, no secret. Registration happens on its own.
- The token issued expires after one hour and renews itself until you revoke it.
2. API key
- For clients offering an API key instead of OAuth.
- Your srn_live_… key goes in X-Api-Key or Authorization: Bearer.
- Create the key in your account, and revoke it in the same place.
Client by client
Claude (claude.ai, Claude Desktop)
Settings, then Connectors, then “Add custom connector”. Paste the URL: Claude discovers on its own that authentication is needed and opens our sign-in window.
Path checked on 31/08/2026.
Claude Code
claude mcp add --transport http sirenic \ https://api.sirenic.eu/mcp/connecteur \ --header "X-Api-Key: srn_live_…"
Without a header, the OAuth flow opens in your browser.
Path checked on 31/08/2026.
ChatGPT
Developer mode must be enabled first: Settings, Apps, Advanced settings, “Developer mode”. Then Settings, Connectors, Create: name, description, the URL above, and OAuth authentication.
Path checked on 31/08/2026.
Le Chat (Mistral)
Settings, Connectors, custom connector, “Streamable HTTP” transport, then the URL. The OAuth authorisation opens at creation time.
Path checked on 31/08/2026.
Perplexity
Settings, “+ Custom connector”, then “Remote”. Two choices work: OAuth (the endpoints are discovered automatically) or API key.
Path checked on 31/08/2026.
n8n
“MCP Client” node, HTTP transport, the URL above, and the X-Api-Key header with your key.
Path checked on 31/08/2026.
What it costs
A verified account gets 100 free calls per month on routes priced at $0.01 or less. Beyond that, each call is charged to your credits at the price shown on the route, exactly like a direct API call: plugging in an assistant changes no price.
What the authorisation allows, and what it does not
- It allows calling the data routes on your behalf, against your quota and then your balance.
- It grants access to neither your email address nor your invoices, and allows neither topping up nor closing the account.
- You cut access off whenever you want: the connector appears among your API keys, marked “Connector”, and is revoked in one click.