Appearance
Connect an AI assistant
This page is for: advisors, forward-deployed engineers and developers who connect AI tools or the CLI.
Built
DutyGraph speaks the Model Context Protocol (MCP) over HTTP. Any MCP client can connect to one endpoint:
text
https://dutygraph.com/api/mcpBy client
| Client | How |
|---|---|
| Claude Code | claude mcp add --transport http dutygraph https://dutygraph.com/api/mcp --header "Authorization: Bearer dgp_..." |
| Claude.ai and Claude Desktop | Settings › Connectors › Add custom connector. Enter the URL, then sign in. |
| ChatGPT | Settings › Connectors › Create. Enter the same URL, then sign in. |
| Cursor and other clients | Add an HTTP server with the URL and an Authorization: Bearer dgp_... header. |
json
{
"mcpServers": {
"dutygraph": {
"url": "https://dutygraph.com/api/mcp",
"headers": { "Authorization": "Bearer dgp_..." }
}
}
}A company's administrator may need to allow custom connectors before employees can add one.
Three surfaces, one protocol
| Surface | Who uses it | Endpoint | Credential |
|---|---|---|---|
| Advisor tools | An advisor's AI assistant | POST /api/mcp | Browser sign-in, or a dgp_ token with read, write and optionally send_email |
| Employee tools | An employee's own AI chat | POST /api/mcp | Browser sign-in, bound to that one person |
| Agent gateway | An issued agent | POST /api/mcp/agent | One dga_ credential per issued agent |
They never share a token.
What the tools will not do
- No tool decides. No tool approves, changes or denies an agent request. Those decisions happen in the DutyGraph app.
- No tool goes around the app. Each advisor tool calls the same server route as the app, as the person who owns the token.
- Writes preview first. Imports and fills return a preview unless you pass
apply: true. - Email needs its own scope.
writenever sends email.