DEPLOY ↗

// 00 — START HERE

QUICKSTART

wspc gives every autonomous agent its own workspace — email, calendar, todo, library — addressed through HTTP, MCP, and a CLI. This page bootstraps one in five minutes.

Two paths below. Pick Hermes if you run the open-source Hermes agent host and want the smallest setup. Pick manual MCP for any other agent host (Claude Desktop, custom, anything that speaks MCP). Both end at the same place.

The agent gets a real inbox, a real calendar, a real todo store. Persistent. Addressable. Yours.

// 01 — HERMES (RECOMMENDED)

HERMES PROMPT PACK

Hermes accepts a declarative MCP server spec. Paste the block below into the agent. Hermes registers the connection, opens the OAuth browser flow when a tool returns 401, and surfaces the verification prompt back through the chat.

No config file. No restart. The pack does the work.

# wspc MCP Server Specification

## Preconditions
- The wspc MCP server is expected to be added to this agent host.
- Connect a custom remote HTTP/SSE MCP server with the following parameters:
  - Name: "wspc"
  - URL: "https://mcp.wspc.ai/mcp"
  - Transport: "sse"
  - Authentication: OAuth 2.1 Remote Flow (discovery, dynamic client registration, browser authorization, email verification via 6-digit magic code, and bearer-token exchange).
- Once connected, you can list and call all wspc MCP tools (calendar, todo, email). If a tool invocation returns a 401 challenge, prompt the user to open their browser for OAuth authorization.

After the pack lands, the first tool call triggers OAuth:

// 02 — MANUAL MCP SETUP

MANUAL MCP SETUP

For any agent host that speaks MCP but does not consume a Hermes-style prompt pack — Claude Desktop, custom orchestrators, MCP-native clients — register the server by hand.

Parameters:

Name:           wspc
URL:            https://mcp.wspc.ai/mcp
Transport:      SSE  (Server-Sent Events over HTTPS)
Auth:           OAuth 2.1 Remote Flow

In Claude Desktop: Settings → Connectors → Add custom connector. Set Name to wspc. Set Remote MCP server URL to https://mcp.wspc.ai/mcp. Click Add.

The host opens the browser. Authorize the same way:

The host stores the token. Tool calls resolve from there.

// 03 — CLI BOOTSTRAP

CLI BOOTSTRAP

You drive wspc from the terminal too. The CLI ships through npx — no global install required.

npx wspc login

The prompt sequence:

Verify the session:

npx wspc whoami     # current identity
npx wspc verify     # validates the cached key

If whoami returns your email, the bootstrap is done. Move to the first calls.

// 04 — FIRST AGENT TASKS

FIRST AGENT TASKS

Three domains. One example each. Real commands. Run them in order or pick the one that matters.

CALENDAR

The calendar persists events, accepts attendees, and ships standard iCalendar (.ics) invites by email. Attendees see a normal invite. The agent sees an event ID.

Create an event for tomorrow at 11:00:

npx wspc event add "Lunch with Friend" \
  --start "tomorrow 11:00am" \
  --end   "tomorrow 12:00pm" \
  --attendee "Friend <[email protected]>"

Expected output:

Event created.
ID:          evt_9b8a7c6d5e4
Title:       Lunch with Friend
Start:       2026-05-23 11:00:00  [local]
End:         2026-05-23 12:00:00  [local]
Attendees:   [email protected]   [.ics dispatched]

List upcoming events:

npx wspc event ls
ID             TITLE                START                END
evt_9b8a7c6d   Lunch with Friend    2026-05-23 11:00     2026-05-23 12:00

TODO

Tasks with optional due dates, hierarchy, and a status field. The agent reads and writes the same store you do.

Add a task that closes tomorrow:

npx wspc todo add "Pay utility bill" --due 2026-05-23
Todo created.
ID:          todo_a7f1c2b3d4e
Title:       Pay utility bill
Due:         2026-05-23
Status:      open

List active tasks:

npx wspc todo ls
ID             TITLE              DUE          STATUS
todo_a7f1c2b3  Pay utility bill   2026-05-23   open

EMAIL

Each account claims aliases under @wspc.app. The alias receives mail, sends mail, and carries the agent’s identity. No gateway. No SMTP relay.

Claim an alias (replace myname with an alphanumeric handle):

npx wspc email alias create [email protected]
Alias created.
Alias:       [email protected]
Created:     2026-05-22 17:47:13
Status:      active

Send a test message to your own external inbox:

npx wspc email send \
  --from    [email protected] \
  --to      [email protected] \
  --subject "wspc test" \
  --text    "Sent from a wspc alias."
Email queued.
Message ID:      em_c8d2f1a0b3c
From:            [email protected]
To:              [email protected]
Subject:         wspc test
Idempotency Key: idem_f9a8b7c6d5e

List received mail for the alias:

npx wspc email ls
ID             SENDER             SUBJECT     RECEIVED
em_c8d2f1a0    [email protected]    wspc test   2026-05-22 17:48

Same commands work from any MCP-connected agent — the tool names map directly: calendar_create_event, calendar_list_events, todo_create, todo_list, email_alias_create, email_send, email_list.

// 05 — KEEP GOING

KEEP GOING

The agent has its workspace now. Hand it work.