What you need
A Junipeer account with at least one integration
The MCP add-on switched on for your organisation. Contact Junipeer if you don't have it yet.
An AI assistant that supports MCP connectors. Most do, for example Claude and ChatGPT.
What is the Junipeer MCP?
MCP (Model Context Protocol) is an open standard that lets AI assistants connect to other services. The Junipeer MCP gives your assistant access to the same information you see in Junipeer: your integrations, their settings, the jobs they have run, and the logs.
You don't need to know where things are in the app or what our technical terms mean. Describe the problem in your own words, for example with your own order number, and the assistant finds the right integration and record for you.
How it fits together
The assistant talks to the Junipeer MCP, which reaches your integrations and, if you want, the systems behind them.
Junipeer MCPWorkspace MCP: your integrations, settings, jobs and logs
The add-on can cover your whole workspace, or only specific connected systems, such as your accounting system. All connectors get MCP support during Q4 2026, except legacy and file-based connectors.
Let the assistant set up the integration
With Workspace MCP you don't have to go through every setting yourself. Once both systems are connected, ask the assistant to set up the rest:
Connect both systems in Junipeer. You add the credentials and OAuth logins yourself, for example for Shopify and Fortnox.
Say what the integration should do. For example: "Help me set up Shopify to Fortnox. Orders should become invoices and payouts should be booked."
Allow it to read your data. The assistant first asks whether it may look at, for example, your last 100 orders, to see which payment methods, countries and VAT rates you actually use. Nothing is changed.
Review the proposal. The assistant proposes the settings section by section, for example which Fortnox terms of payment each payment method should get, and saves only when you say yes.
Test without sending anything. It shows what a real order would become in the ERP, without sending it. With your yes it then runs one order for real, and you check the result in the ERP.
Go live. The assistant switches on the flows and the schedule when you say so.
To save settings and run tests, the assistant needs permission to change settings and run jobs (integrations:config:write and integrations:jobs:run).
You don't need to read every setting
This knowledge base has an explanation for every setting, but you don't need to read them in advance. In Junipeer every setting has a ? that opens the same explanation right next to the form.
The explanation is where you set it
Every setting in Junipeer has a ?. Click it and the explanation opens next to the form.
A blue ? has an explanation. The same texts are in this knowledge base, but you don't need to read them in advance.
If you want to know more, ask the assistant: "What does the setting Create customers in Centra do, and what is it set to now?"
MCP with different systems
Type of system | For example | What you can ask about |
|---|---|---|
E-commerce | Shopify, Centra, WooCommerce | What an order looks like in the shop, which payment and shipping methods your orders use |
ERP | Fortnox, Business Central, Visma.net | Whether an invoice or customer exists, which terms of payment and accounts there are to choose from |
Payments | Klarna, Adyen, Svea | What a payout contained and why a payment wasn't matched to an invoice |
Shipping | nShift, Sendify | Which shipments were created for an order |
How far the assistant reaches in each system depends on your add-on and on what you allow.
What you can ask
About your integrations: which integrations you have, which systems they connect, whether they are active and when they last ran.
About settings: what a setting does, what it is set to now, and whether it explains what you are seeing. Passwords and other secrets are always hidden.
About logs and errors: what happened to a specific order or invoice, why something was skipped, and what an error message means.
About your connected systems: if you allow it, the assistant can also look directly in the systems behind the integration, such as your webshop or accounting system. For example, it can check what an order actually looks like there.
Connect it step by step
Find the MCP address. Log in to Junipeer at app.junipeer.io. The address of your Junipeer MCP is shown in the platform.
Add Junipeer to your AI assistant. In your assistant's settings, add a new connector (sometimes called a custom connector or MCP server) and paste the address.
Sign in with Junipeer. The assistant opens a Junipeer login. Sign in and approve the access. Start with read-only access if you are asked what the assistant may do.
Test the connection. Ask: "Which Junipeer integrations do I have?" If the assistant lists your integrations, the connection works.
If your assistant asks for a client ID and secret
Some assistants and tools use an API key instead of a login:
Go to My account → API keys in Junipeer and create a new key.
Choose what the key may do. Start with read-only:
integrations:read: see your integrations and what they did (jobs and logs)integrations:config:read: see how they are set up (settings)external_api:read(optional): let the assistant read data in your connected systems
Add these only if you want the assistant to make changes:
integrations:config:write: change settings and mappingintegrations:jobs:run: run jobs (this moves real data)external_api:write: write directly to your connected systems
Copy the client ID and secret into your assistant. The secret is shown only once. Don't paste it into a chat.
You can't change what a key may do after you create it. To give the assistant more or less access, create a new key. You can revoke a key at any time under My account → API keys.
What it can and can't change
With read-only access, it can't change anything. It can only look.
Your access decides what's possible. If the assistant tries something it isn't allowed to, Junipeer refuses and says which permission is missing. The assistant can't get around that.
It asks before every change. Before changing anything, the assistant tells you what the setting is now, what it would become and what the change won't fix, and then waits for your yes.
Running jobs and writing to your systems affect real data. Running a job moves real orders, invoices or products between your systems. A direct write to your accounting system or webshop can't be undone from Junipeer. The assistant has to tell you what it's about to send, and to which system, before it does it.
Your secrets stay hidden. Passwords and tokens are shown as
***and are never sent to the assistant.It only sees your organisation. Other organisations' data isn't available.
Logging in to other systems is up to you. If a system needs you to log in, for example to reconnect Fortnox, the assistant gives you the link and you click it yourself.
Tip: Start with read-only access. Add write permissions later, if you find you want the assistant to make changes for you.
Example questions
"Which integrations do I have, and are they all running?"
"Why didn't order 10234 come over to Fortnox?"
"What does the setting 'Import only unfulfilled orders' do, and is it on?"
"Show me the errors from last night's order sync and explain them simply."
"Which payment methods are mapped, and is anything missing?"
"When did the product sync last run?"
If the connection doesn't work
The assistant can't connect or isn't authorised: check that the MCP add-on is active for your organisation and that you signed in with the right Junipeer account. With an API key, check the client ID and secret. If you lost the secret, create a new key.
"This key does not have the … scope": you haven't allowed that action. Give the assistant the missing permission, or keep using read-only.
The assistant can't find your integration: name the integration or the systems it connects, for example "Shopify to Fortnox", and check that you are signed in to the right organisation.
The assistant can't see data in your webshop or accounting system: it needs permission to read your connected systems, and the connection to that system has to work in Junipeer.
Still stuck? Contact Junipeer support and say which assistant you use. Never send your secret to support or anyone else.