Point your copilot at Dagen.
Run this once per workspace. It registers Dagen as an MCP server so Claude, Copilot, or any MCP-compatible agent can discover your Agent Views.
$ claude mcp add dagen https://app.dagen.ai/mcp
# or, via a raw MCP config
{
"mcpServers": {
"dagen": { "url": "https://app.dagen.ai/mcp" }
}
}
Sign in once, governed every time after.
Dagen authenticates against your existing identity provider. Whatever access a user already has determines what their agent can see — nothing more.
→ opening browser to sign in with your workspace SSO…
→ authenticated as tiernan@yourcompany.com
→ 4 agent views available
See what your agent can already reach.
List the Agent Views you're authorized to query. Each one comes with a name, a description, and the definitions an agent needs to use it correctly.
→ revenue_360 — quarterly revenue by account, region, stage
→ support_health — ticket volume, SLA, and account health
→ pipeline_ops — dbt run status and freshness by model
Ask your first question.
That's the whole setup. Every answer comes back tagged with the Agent View and source table it was governed by.
→ answered from agent view revenue_360
→ source: fct_opportunity · governed · 214 ms
Common questions.
Do I need admin access to add the MCP server?+
Adding the server to your own client (like Claude Code or Claude Desktop) doesn't require admin access. Provisioning which Agent Views exist and who can reach them is an admin task, done once per workspace.
Which agents and copilots are supported?+
Any client that speaks MCP — Claude, GitHub Copilot, and custom agents built on the Model Context Protocol. See the MCP reference for the full tool surface.
What if I see zero Agent Views after authenticating?+
That means none have been built yet, or your account hasn't been granted access to any. An admin can create your first Agent View from the Dagen workspace in minutes.
Ready to go deeper?
Read the full MCP reference, or bring your hardest question to a technical demo.