Agents

Connect Daat to agent systems

Connect Claude, terminal tools, and future open-source agents to the same Daat context layer.

Claude connector

This is the path for Claude app experiences, including Claude, Claude Code in the app, and Cowork.

Connections

Loading…

Set up in Claude

This usually takes about 30 seconds.

Open Claude settings → Go to Settings → Connectors
Add a custom connector → Click “Add custom connector” → Give it a name, like “Daat”
Add the MCP server → Paste the MCP URL → Click “Advanced settings”
Paste connection values → MCP URL → Authorize URL → Token URL → Tool name
Complete authorization → Claude will open a Daat consent page → Sign in and approve access
Finalize → When redirected back, click “Configure” → Set to “Always allow”

Terminal

Use this for Claude Code in the terminal, local tools, and generic MCP clients.

Access tokens

Loading…

Set up terminal MCP

Create a token → Name it for the tool or machine → Copy it before closing the window
Add Daat as an MCP server → Use the generic MCP URL → Add your token as the Authorization header
Ask through your tool → Use ask_daat({ question }) → Daat will use workspace-scoped context

MCP config examples

Register Daat as an HTTP MCP server. Exact CLI flags may vary by Claude Code version — if this doesn't match yours, add the same entry to your Claude Code MCP config directly.

claude mcp add daat \
  --transport http \
  --url https://daat-mcp-production.up.railway.app/mcp \
  --header "Authorization: Bearer dk_live_..."

Or drop the JSON config:

{
  "mcpServers": {
    "daat": {
      "type": "http",
      "url": "https://daat-mcp-production.up.railway.app/mcp",
      "headers": {
        "Authorization": "Bearer dk_live_..."
      }
    }
  }
}

Advanced MCP details

Both routes use the same underlying system. The difference is how clients connect.

Claude connector route OAuth

https://daat-mcp-production.up.railway.app/mcp/claude

Tool: daat_company_context({ question }) — tuned output shape for Claude's conversational surface.

Terminal and generic MCP route

https://daat-mcp-production.up.railway.app/mcp

Tool: ask_daat({ question }) — generic MCP output shape.

Auth (generic): Authorization: Bearer dk_live_...
Auth (Claude): OAuth 2.1 with PKCE — create a connection under Claude
Transport: Streamable HTTP (JSON-RPC 2.0)
Scope: workspace-bound, session-aware per token and client session when available
Health: GET /health on the MCP host reports version and active adapters

Test with curl

A valid MCP tools/call against the generic route. Swap the URL to /mcp/claude and the tool name to daat_company_context to exercise the Claude-specific adapter.

curl https://daat-mcp-production.up.railway.app/mcp \
  -H "Authorization: Bearer dk_live_..." \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"ask_daat","arguments":{"question":"What is going on in this company?"}}}'

Open-source agents

Open-source agent frameworks are coming soon. They’ll use the same Daat context layer through MCP, with workspace-scoped tokens and agent session memory.

Coming soon

External agent frameworks

Future adapters will connect open-source agents to Daat without changing the underlying context layer.