Developers & AI agents

Everything a team member can do in Segui, an AI agent or script can do too, through the same rules and only inside your workspace. Segui offers a remote MCP server for AI agents and a REST API with an OpenAPI spec. Agents can also read llms.txt.

Authentication

An admin opens Settings → API & AI agents and clicks Connect agent. Segui creates an API key (sgi_…), shows it once and shows the setup for your tool with the right URL. Send it with every request:

Authorization: Bearer sgi_…

• A key acts as the admin who created it, with the rights chosen for it: member (inquiries, notes, tasks, notifications) or admin (also pipeline, settings and website form links), optionally read only.
• Keys work only in their workspace. They stop working when they are revoked, when their creator leaves the team, and while the workspace is locked by billing.
• Limit: 120 requests per minute per key (HTTP 429 with Retry-After).

Quickstart

The API lives at https://api.segui.app. The first call lists the inquiries whose next step is due, the second creates an inquiry whose next step is due on 1 October (reminderOn is the date of the next step).

curl -H "Authorization: Bearer $SEGUI_API_KEY" https://api.segui.app/api/v1/inquiries/due

curl -X POST https://api.segui.app/api/v1/inquiries \
  -H "Authorization: Bearer $SEGUI_API_KEY" -H "Content-Type: application/json" \
  -H "Idempotency-Key: form-4711" \
  -d '{"familyName":"Muster","firstName":"Anna","email":"anna@example.com","reminderOn":"2026-10-01"}'

MCP setup

The MCP endpoint is https://api.segui.app/mcp (Streamable HTTP, stateless; protocol 2026-07-28 and the earlier 2025 versions).

Claude Code

claude mcp add --transport http segui https://api.segui.app/mcp --header "Authorization: Bearer sgi_…"

Claude Desktop and claude.ai

Settings → Connectors → Add custom connector. URL https://api.segui.app/mcp, header Authorization: Bearer sgi_….

Codex

# ~/.codex/config.toml
[mcp_servers.segui]
url = "https://api.segui.app/mcp"
bearer_token_env_var = "SEGUI_API_KEY"

Hermes

# ~/.hermes/config.yaml
mcp_servers:
  segui:
    url: "https://api.segui.app/mcp"
    headers:
      Authorization: "Bearer sgi_…"

Other MCP clients

{"mcpServers": {"segui": {"type": "http", "url": "https://api.segui.app/mcp",
  "headers": {"Authorization": "Bearer sgi_…"}}}}

Tools and endpoints

Every MCP tool is also a REST endpoint under /api/v1. Resources: segui://workspace, segui://pipeline, segui://team, segui://due-today.

• Inquiries: search_inquiries, list_due_today, get_inquiry, create_inquiry, update_inquiry, move_inquiry, update_inquiry_step, set_reminder, clear_reminder, assign_advisor, unassign_advisor, mark_inquiry_lost, mark_inquiry_invoiced, delete_inquiry, restore_inquiry
• Notes: list_notes, add_note, update_note, delete_note
• Tasks: list_tasks, get_task, create_task, update_task, complete_task, delete_task, restore_task
• Pipeline and team: get_pipeline, update_pipeline, remove_stage, list_team
• Notifications: list_notifications, archive_notification, archive_all_notifications
• Reports (Business): get_report, export_inquiries_csv
• Workspace: get_workspace, update_workspace, list_form_links, create_form_link, revoke_form_link

The next step of an inquiry is its first timeline step that is neither done nor skipped. Its date is the reminder: that day the inquiry shows up in Today and in the notifications of the people assigned. set_reminder sets the date of the next step, clear_reminder removes it, list_due_today lists the inquiries whose next step is due (overdue first), and reminderOn on an inquiry is the same date. Tasks are separate internal to-dos, not part of the timeline.

Conventions

• JSON in and out. Days as YYYY-MM-DD, timestamps as ISO 8601.
• Lists return {"items": [...], "nextCursor": "..."}; pass cursor for the next page.
• Creates accept an Idempotency-Key header (MCP: idempotencyKey); a retry within 24 hours returns the first result.
• Errors: {"error": {"code": "NOT_FOUND", "message": "..."}} with 400, 401, 402 (billing or plan), 403 (role or read only), 404, 409, 429.

OpenAPI

The full spec is served at https://api.segui.app/api/v1/openapi.json and is generated from the same definitions as the MCP tools.