Skip to main content
Worktruck.app exposes a Model Context Protocol server at mcp.worktruck.app. Any MCP-compatible AI client (Claude Desktop, Claude Code, Cursor, etc.) can connect directly to your data.

​
Transport

The MCP server uses Streamable HTTP transport — the standard for remote MCP servers. No local process, no stdio piping. Connect from any MCP-compatible host over HTTPS.

​
Connection

Add this to your Claude Desktop config (or equivalent for other MCP hosts): 
{
  "mcpServers": {
    "worktruck": {
      "url": "https://mcp.worktruck.app/mcp/v1",
      "headers": {
        "Authorization": "Bearer bsk_live_your_key_here"
      }
    }
  }
}
That is the entire setup. Three fields: URL, header name, header value.

​
Claude.ai custom connector (OAuth)

Claude.ai’s custom-connector UI requires OAuth 2.1 with Dynamic Client Registration — it does not accept static API keys. Paste https://mcp.worktruck.app/mcp/v1 into the “Add custom connector” URL field. On first use, Claude.ai discovers the OAuth flow from the server’s WWW-Authenticate challenge, registers itself with Keycloak (auth.builddaddy.app/realms/worktruck) via DCR, and completes PKCE authentication in a browser popup. No manual OAuth client setup on your side.

​
Authentication

The MCP server accepts three credential types:
  • API key (Bearer token) — Authorization: Bearer bsk_live_... for programmatic clients (Claude Desktop, Claude Code, Cursor, scripts)
  • Keycloak-issued JWT — OAuth 2.1 access tokens from auth.builddaddy.app/realms/worktruck with aud=mcp. The Claude.ai connector uses this path automatically; other OIDC-aware clients can use it too
  • x402 payment receipt — per-request agent payments, no account needed
JWT-authenticated requests must send Mcp-Protocol-Version: 2025-06-18. Static-key and x402 requests are exempt.

​
Available tools

​
Per-domain tools (CRUD)

Precise, scoped operations for each domain. The AI uses these when it knows exactly what to do.
DomainToolsDescription
Contactscontacts_search, contacts_get, contacts_create, contacts_update, contacts_delete, contacts_list_relationships, contacts_log_interaction, contacts_find_by_channelPeople, organizations, relationships, interaction history
Taskstasks_list, tasks_get, tasks_create, tasks_update, tasks_complete, tasks_delete, tasks_add_dependency, tasks_add_comment, tasks_search, tasks_list_overdueTask management with subtasks, dependencies, recurrence
Calendarevents_list, events_get, events_create, events_update, events_delete, events_check_availability, events_searchEvents, scheduling, availability
Notesnotes_search, notes_get, notes_create, notes_update, notes_delete, notes_list_backlinksNotes, notebooks, bidirectional links

​
Composite tools (cross-domain)

These combine queries across multiple domains in a single tool call. This is what makes the MCP server uniquely powerful — no other server owns all five domains.
ToolUse caseWhat it returns
daily_briefing”What’s my day look like?”Today’s events with attendee names, overdue tasks, tasks due today and this week
prepare_for_meeting”Brief me on my next meeting”Event details, attendee contact cards, interaction history, related tasks and notes
context_for_person”What’s my relationship with Sarah?”Full contact card, interaction history, shared tasks, upcoming events, linked notes

​
Resources

MCP resources provide read-only views of your data:
ResourceDescription
contacts://recentRecently updated contacts
tasks://pendingTasks that are not yet complete
calendar://upcomingUpcoming calendar events

​
Dynamic domain filtering

Only the domains you actively use appear as available tools. If you have no calendar events, calendar tools are deprioritized. This keeps the tool list clean and reduces noise for the AI.