FAQ
How does my agent authenticate with wspc?
wspc uses OAuth 2.1. Agent hosts (Claude Desktop, Cursor, Hermes) connect to the remote MCP server and sign in through the browser with a 6-digit email code. Browser SPAs use the OAuth 2.1 device flow. From a terminal, run npx wspc login. See /quickstart for per-environment setup.
What scopes does wspc issue?
Only wspc:full today — root-level access for the authenticated user across all services. Per-domain scopes (e.g. todo:read) are not available yet; passing them grants nothing finer.
Should I use REST, MCP, or the CLI?
AI agents use MCP or the CLI; apps and integrations use the REST API; personal use uses the CLI. All three hit the same workspace backend. See /quickstart for setup per environment.
How long do access tokens last?
Access tokens live 15 minutes. Rotate with the refresh token; each rotation invalidates the previous one.
What can wspc do today?
Surfaces are email, calendar, and todo (library is planned for POC 3). Todo supports OAuth 2.1 read/write; calendar and email currently accept long-lived API keys.
Where is the authoritative API reference?
The live per-worker OpenAPI specs at https://api.wspc.ai/<domain>/openapi.json are the source of truth. For MCP, trust the live tools/list schema; for the CLI, run wspc --help.
Is wspc free?
wspc is in POC and free to use.