Publishing an Integration in the Marketplace
Do you offer software or a service that makes work easier for public administrations? You can offer your solution as an integration in the Ayunis Core Marketplace. Administrations can then install it in Ayunis Core with just a few clicks. This page explains what you need to do.
How Integrations Work: MCP
Section titled “How Integrations Work: MCP”Integrations in Ayunis Core are based on the Model Context Protocol (MCP). MCP is an open standard that lets AI applications work with external services. Your service provides tools through a so-called MCP server — for example “search council documents” or “create appointment”. The AI in Ayunis Core recognizes these tools and uses them automatically when they fit the question.
For you, this means: you don’t need a dedicated interface just for Ayunis Core. An MCP server is all it takes — and it also works with other AI applications that support MCP.
What Information We Need
Section titled “What Information We Need”About Your Integration
Section titled “About Your Integration”This information will appear in the marketplace:
| Information | Explanation |
|---|---|
| Name | The name of your integration in the marketplace |
| Short description | One or two sentences for the overview (maximum 300 characters) |
| Full description | What your integration does and who it is for |
| Logo | As PNG, SVG, WebP, or JPEG, maximum 2 MB |
| Benefits | A few bullet points on the value for administrations |
| Example | A typical question to the AI and the answer your integration makes possible |
Technical Details
Section titled “Technical Details”We need this information to set up your integration in Ayunis Core:
| Information | Explanation |
|---|---|
| MCP endpoint | The URL of your MCP server |
| Authentication method | How Ayunis Core signs in to your server: no authentication, API key (bearer token), a custom HTTP header, or OAuth |
| Settings during installation | Which details administrations must enter during setup (e.g., API key or tenant ID) — each with a label, a short help text, and whether it is entered once for the whole organization or by each person individually. For a custom HTTP header, also its name. |
| OAuth details (OAuth only) | Authorization URL, token URL, required scopes, and whether the connection is made once for the whole organization or by each person individually |
| Test access | Credentials we can use to test your integration |
Legal and Contact
Section titled “Legal and Contact”| Information | Explanation |
|---|---|
| Terms of use (if applicable) | Link to the terms administrations must accept during installation, and their version |
| Contact person | Name, organization, email address, and optionally a phone number |
How Publishing Works
Section titled “How Publishing Works”- Send an email: Send all the information to partnerships@ayunis.com. Attach your logo to the email.
- Testing: We set up your integration in Ayunis Core and test it. If we have questions, we will contact you.
- Publishing: Once testing is successful, we publish your integration in the marketplace. From then on, administrations can install it.