Plugins

Submitting Your Plugin

Updated on August 2, 2026

Publication and submission process

Once your plugin is fully developed, tested, and deployed, you can submit it to Talqui for publication in the platform's plugin catalog. This page explains what you need to submit, how to submit it, and what happens next.

What Talqui needs

To publish your plugin, Talqui requires the public addresses of the elements you built. You only need to provide addresses for the elements you included:

Element	What Talqui needs	Example
Backend API	Public HTTPS URL to your REST API root	`https://api.example.com`
MCP Endpoint	Public HTTPS URL to your MCP endpoint	`https://api.example.com/mcp`
Widget	Public HTTPS URL to your widget SPA	`https://widget.example.com`
Settings	Public HTTPS URL to your settings SPA	`https://settings.example.com`

If your plugin does not include a widget or settings page, simply omit those addresses. If your plugin is backend-only (no UI), you only need the API and MCP addresses.

All addresses must be publicly accessible over HTTPS. Talqui will validate each endpoint during the review process.

Additional information

Beyond the addresses, you may also need to provide:

Authentication credentials your plugin requires (API keys, OAuth links, workspace IDs, etc.)
Configuration notes explaining how Talqui should set up or test the plugin
Support contact for Talqui to reach you if issues arise

How to submit

Send your submission to developer@talqui.com with the subject line Plugin Submission: [Your Plugin Name].

Use the template below as your email body. Fill in all the required fields and omit sections for elements you didn't build:

=== PLUGIN SUBMISSION ===

Plugin Name: [Your plugin name]
Brief Description: [One paragraph describing what your plugin does]

--- DEPLOYMENT ADDRESSES ---

Backend API:
URL: https://...
MCP Endpoint: https://...

Widget:
URL: https://... (if present)

Settings:
URL: https://... (if present)

--- AUTHENTICATION & CONFIGURATION ---

Required Credentials:
[List any API keys, OAuth links, workspace IDs, or other setup the platform needs]

Configuration Notes:
[Explain how to set up or test the plugin, if necessary]

Support Contact:
Name: [Your name]
Email: [Your email]
Phone: [Optional]

--- ADDITIONAL INFO ---

Repository URL: https://github.com/... (if public)
Documentation URL: [Your plugin's docs, if any]
Any other notes: [Anything else Talqui should know]

=== END SUBMISSION ===

Replace the placeholders with your actual information, and send it to developer@talqui.com.

Review and approval process

Once Talqui receives your submission:

Initial review — Talqui's team validates that:
- All provided addresses are publicly accessible
- The plugin meets the platform's security and integration standards
- Your authentication approach is correct (see Authentication)
Functional testing — Talqui exercises:
- Every MCP tool via the MCP Inspector
- Every REST route with sample data
- Widget and settings UIs (if present) in a test environment
Approval or feedback — Talqui will either:
- Approve — your plugin is published and appears in the plugin catalog
- Request changes — Talqui will explain what needs to be fixed; update your plugin and resubmit
Publication — Once approved, your plugin becomes available immediately in the platform's install catalog. Tenants can install it, configure it (via your settings page if present), and operators can use it (widgets if present).

After publication

Once your plugin is live:

Tenants install it — they enter your plugin on the platform and configure it through your settings page (if any)
Operators use it — they see your widget in conversations and can use your MCP tools (if any) in automated procedures
You maintain it — fixes, improvements, and new features are entirely on your side. Deploy updates independently without requiring platform changes.

If you need to update your plugin after publication, simply deploy the new version to your endpoints. Talqui always calls the latest version; no re-approval needed.

Troubleshooting

My plugin was rejected. What now?

Talqui's team will explain what didn't meet standards. Common issues include:

Missing or inaccessible endpoints
Incorrect authentication headers
MCP tools not responding correctly
Security or data-handling concerns

Fix the issues and resubmit via email.