Skip to main content
Imagine an agent that answers policy, product, and FAQ questions by looking them up in your docs—concise, cited, and available right inside chat without derailing the conversation.

​
What You’ll Build

  • A Mastra agent that can participate in conversations as a documentation expert.
  • Triggered only when explicitly mentioned (e.g., @agent).
  • Can fetch knowledge from your docs and return short, sourced answers.
  • Integrated into CometChat chats.

​
Prerequisites

  • A Mastra project (npx create-mastra@latest my-mastra-app).
  • Node.js installed.
  • OpenAI API key in .env as OPENAI_API_KEY.
  • A CometChat app.

​
How it works

This example implements a retrieval-augmented Knowledge Agent that:
  • Ingests sources (URLs, files, or raw text) into a local knowledge folder per namespace using the ingestSources tool. Parsed content is stored under knowledge/<namespace> for repeatable retrieval.
  • Retrieves relevant snippets with the docsRetriever tool. It scans your knowledge/<namespace> content, chunks and ranks results, and returns the best matches with source metadata.
  • Generates answers using only retrieved context. The agent replies when invoked (e.g., @agent), composes a concise answer, and appends a short “Sources” list with citations.
  • Handles errors defensively. Server utilities sanitize errors before returning responses.
Key components (source-linked below): the agent, docs retriever tool, ingest endpoints, and server routes.

​
Setup

1

Prepare project

Create a Mastra app and add OPENAI_API_KEY in .env. See the repository README for exact steps.
2

Define the agent

Add a knowledge agent that answers from retrieved docs only, and responds when explicitly mentioned (e.g., @agent).
3

Register in server

Register the agent and expose endpoints for /api/tools/ingestSources, /api/tools/searchDocs, and /api/agents/knowledge/generate (see server entry).
4

Ingest knowledge

Choose a namespace (e.g., docs) and POST sources to /api/tools/ingestSources. Use URLs, file paths, or raw text. Request shape is documented in the README Quickstart.
5

Ask the agent

Send chat turns to /api/agents/knowledge/generate with a messages array. Optionally pass toolParams.namespace to scope retrieval.
6

Connect to CometChat

In Dashboard → AI Agents, set Provider=Mastra, Agent ID=knowledge, and point Deployment URL to your public generate endpoint.
7

Deploy & observe

Make the API public, verify via Swagger UI, and re-run ingestion when docs change.

​
Project Structure

Core files and folders for the Knowledge Agent (browse source on GitHub):

​
Step 1 - Create the Agent

src/mastra/agents/knowledge-agent.ts (view in repo): Checklist for the agent:
  • Set name to “knowledge” so the API path is /api/agents/knowledge/*.
  • Respond only when mentioned (e.g., @agent).
  • Answer from retrieved docs and include a short “Sources:” list.
  • Register docsRetriever.

​
Step 2 - Register the Agent in Mastra

src/mastra/index.ts (view in repo):
  • Server entry: src/mastra/index.ts
  • Ensure the agent is registered with key “knowledge” → API path /api/agents/knowledge/*.
  • Storage/logger configuration as per repo README.md.

​
Step 3 - Run the Agent

Dev script & local server details are tracked in your repo: Expected local API base: http://localhost:4111/api
1

Install dependencies

Use the commands in the Quickstart (kept in the repository).
2

Start the dev server

Follow the Quickstart to run the local Mastra server.
3

Ingest sources

POST to /api/tools/ingestSources with a namespace. Example commands are in the README Quickstart.
4

Ask the knowledge agent

POST to /api/agents/knowledge/generate. See the README Quickstart for request bodies and examples.
API endpoints exposed by this example (see Swagger UI):
  • POST /api/tools/ingestSources — ingest URLs/files/text into knowledge/<namespace>
  • POST /api/tools/searchDocs — retrieve relevant snippets from knowledge/<namespace>
  • POST /api/agents/knowledge/generate — chat with the agent

​
Step 4 - Deploy the API

Ensure the public route: /api/agents/knowledge/generate is reachable.

​
Step 5 - Configure in CometChat

1

Open Dashboard

Open the CometChat Dashboard.
2

Navigate

Go to your App → AI Agents.
3

Add agent

Set Provider=Mastra, Agent ID=knowledge, Deployment URL=your public generate endpoint.
4

(Optional) Enhancements

Add greeting, prompts, and configure actions/tools if you use frontend tools.
5

Enable

Save and ensure the agent toggle shows Enabled.
For more on CometChat AI Agents, see the docs: Overview · Instructions · Custom agents

​
Step 6 - Customize in Chat Builder

1

Open variant

From AI Agents click the variant (or Get Started) to enter Chat Builder.
2

Customize & Deploy

Select Customize and Deploy.
3

Adjust settings

Theme, layout, features; ensure the Mastra Knowledge agent is attached.
4

Preview

Use live preview to validate responses & any tool triggers.

​
Step 7 - Integrate

Once your Knowledge Agent is configured, you can integrate it into your app using the CometChat No Code - Widget:
Widget

No Code - Widget

React

React UI Kit

Pre Built UI Components
Note: The Mastra Knowledge agent you connected in earlier steps is already part of the exported configuration, so your end-users will chat with that agent immediately.

​
Step 8 - Test Your Setup

1

API generates response

POST to /api/agents/knowledge/generate returns a doc-grounded answer.
2

Agent listed

/api/agents includes “knowledge”.
3

Tool action works

UI handles docsRetriever tool invocation.
4

Full sample test (run curl)

See curl command below.
curl -X POST http://localhost:4111/api/agents/knowledge/generate \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      { "role": "user", "content": "@agent where is the refund policy documented?" }
    ]
  }'

​
Security & production checklist

  • Protect endpoints with auth (API key/JWT) and restrict CORS to trusted origins.
  • Add basic rate limiting and request size limits to ingestion and generate routes.
  • Validate inputs: enforce allowed namespaces, URL/file whitelists, and payload schemas.
  • Monitor logs and errors; sanitize responses using server utilities.
  • For public deploys, keep your OpenAI key in server-side env only; never expose it to the client.

​
Troubleshooting

  • Agent talks too much: tighten instructions to only respond when mentioned and to answer from docs.
  • No results: ensure /knowledge contains .md/.mdx files or your ingestion job populated the store.
  • Not visible in chat: verify the agent is added as a user in CometChat and enabled in the Dashboard.
  • 404 / Agent not found: check that the server registers the agent with key knowledge.

​
Next Steps

  • Add tools like summarize-doc, fetch-policy, or link-to-source.
  • Use embeddings + chunking for better retrieval.
  • Restrict answers to whitelisted folders or domains.
  • Inspect and try endpoints via Swagger UI (/swagger-ui).
  • Set up CI/CD in your own repo as needed.
⌘I