Configure MCP connectors so mentors can call external MCP tools and return results inside the chat.
- Featured connectors: prebuilt/default (some open-source) you can enable
- Custom connectors: define your own endpoint and authentication
- Go to MCP → Custom Connectors → Add.
- Fill the fields:
- Image (optional)
- Name
- URL (connector/server URL)
- Description (optional)
- Transport type
- Authentication method:
- None
- API Key
- Token type for the header (e.g., Bearer, Basic, Token)
- Token value
- Click Connect to save.
- The connector appears in your list.
- You can enable/disable any connector.
- Disabling prevents mentors from using that MCP server in replies.
- In the MCP provider, copy the Access URL and Access Token.
- In MCP → Custom Connectors, set:
- Name: e.g., Workflow MCP
- URL: paste the access URL
- Auth: API Key
- Token type: Bearer
- Token value: paste the token
- Click Connect.
- The connector is added and can be toggled on/off.
- Grab a project ID from your MCP workspace.
- Ask the mentor, for example:
- “List the workflows in the project
<PROJECT_ID>.”
- “List the workflows in the project
- The mentor lists active workflows (e.g., FAQ, webhook test, etc.).
- Run a workflow, for example:
- “Execute the FAQ workflow and tell me: How do I reset my password?”
- The mentor includes your question in the workflow request body and returns the answer from the MCP server.
Your mentors can call enabled MCP connectors to list resources and execute workflows, returning MCP-sourced answers directly in the conversation.