Reach the same tools over MCP
The same tools, served over the Model Context Protocol on Streamable HTTP. It takes the same Bearer token as the rest of this API, and a client reads the tool list and the schemas with MCP's own tools/list, which is why neither is written out here.
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Response Body
application/json
text/plain
curl -X POST "https://example.com/mcp"{ "jsonrpc": "string", "id": null, "method": "string", "params": {}, "result": {}, "error": {}}mail_message_send POST
Send an email message from the requester's connected mail account. Provide at least one recipient in 'to', a subject, and a body. Requires approval before sending. `external_send` · approval · v1
Keep my picture POST
The picture the member set on their messenger, or when there is none the gradient the app draws from their email, sent in the `file` field of `multipart/form-data` as PNG, JPEG, WebP, GIF, HEIC or HEIF and kept as that member's picture. A notification cannot draw, so it can only show a picture that is kept. A picture kept through this endpoint is replaced by a new one; a picture set anywhere else, or the same picture again, is left as it is and `kept` is `false`.