Ejento AI
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Guides
QuickstartRecipesREST APIsRelease NotesFAQs
Ejento AI
  1. Guides
  • Basic Operations
    • Features
      • Organization → Projects → Assistants → Teams Hierarchy
    • Guides
      • Login/Signup
  • Assistants
    • Overview
    • Features
      • Assistant Access Control
      • Assistant Evaluation
      • Evaluation Metrics
      • URL-based Chat Thread Creation and Prepopulation
      • Reasoning Patterns
      • Staging & Publishing
    • Guides
      • Add Assistant
      • Evaluate Assistant
      • Edit Assistant
      • Assistant Edit Access
      • Embed Assistant
      • Delete Assistant
      • Add Favourite Assistants
      • View Assistant Id
      • Voice Calling with Assistants
  • Corpus
    • Overview
    • Features
      • Corpus Permissions
      • PII Redaction
      • ETag Setup for Corpus Incremental Refresh
    • Guides
      • Assistant Corpus Setup
      • Assistant Corpus Settings
      • Corpus Access Control
      • Corpus Connections
      • View Corpus Id
      • View Document Id
      • Tagging
        • Corpus tagging
        • Document tagging
  • Teams
    • Overview
    • Guides
      • Add a Team
      • Edit a Team
      • Delete a Team
      • View Team Id
  • Projects
    • Overview
    • Guides
      • Add a Project
      • Edit a Project
      • Managing Assistants in a Project
      • Delete a Project
      • View Project Id
  • User Settings
    • Overview
    • Features
      • Ejento AI User Access Levels
    • Guides
      • Add new user
      • Invite Users via Link or Email
      • View my User Id
  • API Keys
    • Overview
    • Guides
      • How to generate API Key and Auth Token
  • Workflows
    • Overview
    • Features
      • Workflow Access Control
    • Guides
      • Add Workflow
      • Workflow Chat
      • Workflow Edit Access
  • Tools
    • Overview
    • Guides
      • Tools Overview
      • Create External Tool
      • Connect Tool to Assistant
  • Analytics
    • Overview
    • Guides
      • Analyzing Data in the Analytics Dashboard
  • Chatlogs
    • Overview
    • Guides
      • Managing Chatlogs
      • View Chatlog & Chat thread Id
  • Integrations
    • Overview
    • Guides
      • Email Indexing
      • Microsoft Teams
      • Sharepoint Indexing
      • Google Drive Connector
      • MS Teams Integration Setup
      • Creating a Connection in Credential Manager
      • Slack App
      • Discord Bot
  • Ejento AI Shield
    • Overview
    • Features
      • Understanding Guardrails
    • Guides
      • How to enable Guardrails
  • Assistant Security
    • Overview
    • Features
      • Assistant Red Teaming
    • Guides
      • Red Team an Assistant
  • Permission Sets
    • Overview
    • Guides
      • Add Permission Set
  • Usage
    • Overview
    • Guides
      • Set Spend Limits
  1. Guides

Create External Tool

In this guide, you add your own external tool, called a custom connector, by linking Ejento AI to an MCP server. Once it's created, the connector appears on the Tools tab, and assistant owners can switch it on for their assistants.
Open the Tools section. If you're not sure how, see Tools Overview.
Only Global Admins can access the Tools section in Organization settings.

How custom connectors work#

A connector is an external tool. It lets an assistant use an outside service, such as a code repository, a database, or a business app, through that service's MCP server. MCP stands for Model Context Protocol. An MCP server receives requests from your assistant and sends back results from the service.
When you create a connector, you give Ejento AI the MCP server's address and how to talk to it. Ejento AI then lists the connector on the Connectors tab as Connected, and adds it to the Tools tab as an External tool that's already Enabled. It isn't switched on for any assistant until an owner turns it on.
Ejento AI also provides ready-made connectors on the Connectors tab. If the service you need is already there, click its Connect button instead of creating a custom connector.

Use cases#

Internal systems: Your engineering team runs an MCP server for your internal knowledge base. Add it as a custom connector, so an engineering assistant can look up internal documentation.
A service without a ready-made connector: A vendor gives you the MCP server address for their product. Add it yourself instead of waiting for a built-in connector.
Access that needs a key: Your MCP server requires an API token. Add the token as a header when you create the connector, so Ejento AI sends it when connecting to the server.

Key terms#

MCP Server URL: The web address of the MCP server that handles the connector's requests. The service's provider or your own team gives you this address.
Transport: The way Ejento AI communicates with the MCP server.
Header: Extra information Ejento AI sends when connecting to the MCP server, used for authentication and authorization, such as an Authorization header with a bearer token.

1. Open the Connectors tab#

On the API Tools page, click the Connectors tab. Each card is an external tool:
Connected: the connector is set up and appears on the Tools tab.
Connect: the connector is available but not set up yet. It doesn't appear on the Tools tab, so assistants can't use it until you connect it.
Step 1 screenshot

2. Start a custom connector#

Click Add Custom Connector. The Add Custom Connector form opens.
Step 2 screenshot

3. Enter the connector and server details#

Fill in these fields:
Name: what assistant owners see in their tool list. Required.
Details: a short description of what the connector does. It appears under the name in tool lists, so owners know when to use it.
MCP Server URL: the address of the MCP server. Required.
Transport: the communication method Ejento AI uses with the server. Required. Choose Streamable HTTP or SSE (Server-Sent Events), whichever your MCP server supports. Check the server's documentation, or ask its provider, if you're not sure.
Step 3 screenshot

4. Add the category, website, and icon#

Fill in the rest of the form:
System Prompt: optional. You can leave it empty.
Category: the kind of service the connector links to, such as Development or Communication. Required. The category appears on the connector's card and is used by the Category filters.
Website: the service's website. Required.
Icon: the image shown on the connector's card. Required. Drag an image into the box or click to select one (PNG, JPG, or WebP, up to 5 MB).
Step 4 screenshot

5. Add authentication and create the connector#

If your MCP server needs sign-in details, add them before you create the connector:
OAuth: turn this on if the server uses OAuth authentication, then choose the sign-in provider under OAuth App Name.
Headers: enter a Key and Value for each header the server needs, for example the key Authorization with the value Bearer <your token>. Click Add Header for more rows.
Then click Create Connector. The message Tool added successfully appears.
Step 5 screenshot

6. Check the new connector#

The form closes, and your connector appears on the Connectors tab as Connected. It's also listed on the Tools tab as an External tool, with Enabled on and Default off.
To change the connector later, click its Connected button. Its Settings tab lets you edit the fields, and Disconnect removes the connection.
Step 6 screenshot
To let an assistant use your new connector, see Connect Tool to Assistant.

FAQs#

What's the difference between Disconnect and Delete Tool?#

Disconnect removes the connector's connection, after you confirm. Delete Tool, in the connector's Settings tab, permanently deletes the connector, and you can't recover it.

Do I need to fill in Headers or OAuth?#

Only if your MCP server needs sign-in. Use Headers for a key your whole organization shares, and OAuth when each person should sign in with their own account. A server that needs neither works without them.
Previous
Tools Overview
Next
Connect Tool to Assistant