Wbijam for AI assistants
Wbijam is a social planning app. Somebody proposes a plan to their crew, everybody answers with one tap, and the plan plus the answers stay in one place. This connector lets an AI assistant do the same on behalf of the account owner: read their plans, create one, send a proposal to people from their crew, and answer a proposal they received.
Endpoint
The server speaks Model Context Protocol over streamable HTTP, in the sessionless revision
2026-07-28 and in the older revisions negotiated through initialize
(2025-11-25, 2025-06-18, 2025-03-26), so current and older
clients both work.
| Item | Value |
|---|---|
| MCP resource | https://wbijam.app/mcp |
| Authorization server | https://wbijam.app |
| Protected-resource metadata | /.well-known/oauth-protected-resource/mcp |
| Authorization-server metadata | /.well-known/oauth-authorization-server |
| Scope | mcp |
Both metadata documents are public and readable without signing in. The tool calls themselves
require the account owner's credential, so an unauthenticated call returns 401 with a
WWW-Authenticate challenge pointing at the metadata above.
How a person connects
In a browser. The client registers itself dynamically, and authorization uses
the authorization-code flow with PKCE (S256). The person lands on a Wbijam consent page,
enters their phone number, receives an SMS code, and presses the button that grants access. An
access request stays valid for 15 minutes.
In a local client. The person creates a key in the app under
Settings → AI assistant and pastes it into the client as a bearer token. The key is
shown once and starts with wbk_.
What the assistant can do
| Tool | What it does |
|---|---|
list_plans | Lists this person's plans, either upcoming or already past. Each entry carries what, when, where, who organises it, this person's answer and who is in. |
get_plan | Shows one plan in detail. For this person's own proposal it adds who is in and who has not answered yet. |
create_plan | Creates a plan. With nobody named it is a solo plan nobody hears about. With names from the crew it is an ordinary proposal: people receive it exactly as they would from the app, notification included. |
answer_plan | Answers somebody else's proposal with one of: in, undecided, not this time. |
time_summary | Summarises how this person spent their time: what they did, where they were and who with. |
Times are given in ISO 8601. 2026-09-05T18:30 means the person's local time, while an
explicit offset or Z means exactly what it says. Anything that is not a time is refused
with a hint, never guessed. Names are not guessed either: a name matching two people in the crew is
refused together with the candidates, and a name matching nobody is refused together with the crew.
What the connector cannot do
- It grants exactly what the account owner already has in the app, and nothing beyond it. Every call runs through the same server functions the app uses, so mutes, blocks, quiet hours, weekly proposal limits and name visibility all behave identically.
- It reaches one account only. There is no access to anybody else's account or data.
- Sending a proposal is visible to other people and delivers notifications to them, so it is worth telling the assistant explicitly when it should send something.
- It does not sign the person out of their phone. This is a separate credential, not a device session.
Lifetimes, revocation and rate limits
| Item | Value |
|---|---|
| Access token (browser) | 30 days |
| Refresh token | 90 days, rotated on every use |
| Key pasted into a local client | no expiry |
| Live keys per account | up to 10 |
| Rate limit | 60 calls per minute per credential, refused with Retry-After |
The person revokes access in the app under Settings → AI assistant. Revoking kills the grant and every token hanging on it in the same moment. Connecting the same client again replaces the previous grant rather than adding a second one. Deleting the account removes the keys with everything else.
Requirements
A Wbijam account is required, and accounts are created in the app with a phone number and an SMS code. The consent page does not create accounts: a number without an account is refused with a note to sign up in the app first. Wbijam is currently published in Polish.
Data and privacy
We process the data needed to run the app, keep it safe and improve the product. What we collect, why, and the rights you have: Privacy Policy. Account deletion: Delete account.
Support
Write to kontakt@wbijam.app.