Third-party Integrations¶
PrimeThink agents connect to external services through several mechanisms, each suited to a different kind of integration. This page is a map of the options — each links to its full documentation.
Ways to Integrate¶
| Mechanism | What it does | When to use it |
|---|---|---|
| API Capabilities | Call any external REST API as an agent tool, with settings placeholders for secrets (${API_KEY}) | The service has an HTTP API and you want the agent to call it directly |
| MCP Capabilities | Attach hosted Model Context Protocol servers (e.g. GitHub's official MCP server) | The service offers an MCP server, giving the agent a full tool suite at once |
| Tool Plugins | Custom tools with your own logic | You need behaviour beyond a single API call — validation, chaining, transformation |
| Email Integration | Send and receive email from chats | Email-based workflows: intake, notifications, correspondence |
| Computer Use Capabilities | Let the agent operate a browser | The service has no API — the agent works through its web UI |
Authentication and Secrets¶
Never hard-code credentials in a capability or tool configuration. Store secrets as settings and reference them with ${SETTING_NAME} placeholders — they're resolved at runtime from your user or group settings. See Settings placeholders.
Integrating from the Other Direction¶
If you want an external system to drive PrimeThink (rather than PrimeThink reaching out), use the REST API with API key authentication, or embed PrimeThink in your site with the Live Chat Widget.