Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions guides/ai-agents/mcp-servers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,7 @@ Once an MCP server is connected to an agent, the agent can use its tools as part
- **Notion** — search docs, read pages, and create new pages from agent findings. See [Get started with Notion MCP](https://developers.notion.com/guides/mcp/get-started-with-mcp).
- **Linear** — file issues from anomalies the agent spots, comment on tickets, query project status. See [Linear MCP docs](https://linear.app/docs/mcp#general).
- **Confluence** — search the knowledge base for context before answering, or publish summaries. See [Getting started with the Atlassian Remote MCP Server](https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/).
- **Lightdash Docs** — give agents access to the complete Lightdash documentation so they can answer questions about Lightdash concepts, configuration, and best practices. URL: `https://docs.lightdash.com/mcp`, auth type `None`. See [Lightdash Docs MCP](/references/integrations/lightdash-mcp#lightdash-docs-mcp).
- Any other service that exposes a remote MCP server (GitHub, Jira, Slack, internal tooling, etc.)

The agent decides when to call MCP tools based on the user's question and the agent's instructions, the same way it decides when to query your data.
Expand Down
Loading