Docs · api
Connections And MCP
Current Teamday API guidance for external tools, data connections, MCP servers, and webhook events.
Teamday connects agents to external systems through MCP servers, files and connected repositories, org secrets, and webhooks.
Use the OpenAPI spec as the source of truth:
https://app.teamday.ai/api/openapi.json
MCP Endpoint
| Method | Path | Purpose | Auth |
|---|---|---|---|
POST | /mcp | Send MCP JSON-RPC or Streamable HTTP messages | OAuth mcp scope |
GET | /mcp | Open an MCP Streamable HTTP session | OAuth mcp scope |
DELETE | /mcp | Close an MCP session | OAuth mcp scope |
OAuth metadata:
https://app.teamday.ai/.well-known/oauth-authorization-server
https://app.teamday.ai/.well-known/oauth-protected-resource
Remote MCP Clients
Connect your MCP client to https://mcp.teamday.ai/mcp. Teamday CLI login and MCP client login use separate credentials.
For Codex:
codex mcp add teamday --url https://mcp.teamday.ai/mcp
codex mcp login teamday --scopes mcp
If Codex runs on a remote host, its browser callback may point to http://127.0.0.1:<port>/callback/.... Your laptop's browser cannot reach the remote host through that address. Leave the login process running, copy the full callback URL from the browser, and run this in a second terminal on the remote host:
curl 'PASTE_FULL_CALLBACK_URL_HERE'
Keep the single quotes so the shell preserves the URL's query parameters. Use the callback from the current login attempt. If the listener has stopped or authorization has expired, restart login.
For Teamday's own CLI, device login avoids callbacks entirely. Other MCP clients can use device authorization only if they implement that grant; server support does not automatically change a client's login flow.
Data Blocks
Data-block queries use:
POST /api/data-blocks/query
Queries are read-only and scoped to the organization.
Webhook Events
Configure durable work event delivery through:
PUT /api/messaging-integration
GET /api/messaging-integration/deliveries
POST /api/messaging-integration/deliveries/{id}/redeliver
POST /api/messaging-integration/signing-secret/rotate
Webhook deliveries include stable event IDs and Teamday-Signature HMAC-SHA256 verification. Configure event_types as exact event names or wildcard families such as job.*; an empty list means all events. Every send attempt is recorded in the delivery ledger with status, HTTP status, attempt number, duration, and redacted destination host. Owners can redeliver a retained event from the ledger; Teamday signs the replay with the current webhook signing secret and records the new attempt.