Create estate guest visit invites and read your Clannit notifications (including past invite codes…
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Create a guest visit invite. Visit times are built in Lagos (WAT) by a CLI step — do not pass step_18_body_from_* hour fields. Collect guest first AND last name before preview. Always emit_display preview before Confirm. After success, display_data.invite_code MUST be the exact numeric data.code / guest_invite_code — never redact or hide for privacy.
Guest last name (required — ask in input form if user only gave one name)
Guest first name (required)
Optional end in WAT. Prefer visit_duration_hours when user gives a duration.
Optional start in Lagos time (WAT), e.g. 2026-10-06T22:30. Omit for “from now”.
Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.
Hours from visit start (default 2). Use for “from now for 2 hours”.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http mcp-bgpt-clannit https://nova.civai.co/mcp/agents/mcp-bgpt-clannit
Create a guest visit invite. Visit times are built in Lagos (WAT) by a CLI step — do not pass step_18_body_from_* hour fields. Collect guest first AND last name before preview. Always emit_display preview before Confirm. After success, display_data.invite_code MUST be the exact numeric data.code / guest_invite_code — never redact or hide for privacy.
| Argument | Type | Description |
|---|---|---|
| visit_end_wat | string | Optional end in WAT. Prefer visit_duration_hours when user gives a duration. |
| guest_last_name* | string | Guest last name (required — ask in input form if user only gave one name) |
| visit_start_wat | string | Optional start in Lagos time (WAT), e.g. 2026-10-06T22:30. Omit for “from now”. |
| guest_first_name* | string | Guest first name (required) |
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| visit_duration_hours | number | Hours from visit start (default 2). Use for “from now for 2 hours”. |
{
"type": "object",
"required": [
"guest_first_name",
"guest_last_name"
],
"properties": {
"visit_end_wat": {
"type": "string",
"description": "Optional end in WAT. Prefer visit_duration_hours when user gives a duration."
},
"guest_last_name": {
"type": "string",
"description": "Guest last name (required — ask in input form if user only gave one name)"
},
"visit_start_wat": {
"type": "string",
"description": "Optional start in Lagos time (WAT), e.g. 2026-10-06T22:30. Omit for “from now”."
},
"guest_first_name": {
"type": "string",
"description": "Guest first name (required)"
},
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
},
"visit_duration_hours": {
"type": "number",
"description": "Hours from visit start (default 2). Use for “from now for 2 hours”."
}
}
}Run the fetch_external_resource_file pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the fetch_forum_announcements pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the fetch_forum_profile_photo pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Marketing/promo advertisement cards for guest invites on the estate (image + open ad link). Do NOT use for invite history, sent invite links, or visitor list — use fetch_notifications instead. GET .../guest-invite/advert (steps 1, 16, 17). Agent-only; hidden from chat suggestion buttons.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Notifications feed for the logged-in resident, including past guest invites created (names, codes, times). Use for: notifications, invite history, guest-invite activity, check my history. Auth probe before create_guest_invite. GET /notification (steps 1, 2, 15).
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the fetch_resource pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the fetch_user_profile_picture pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the fetch_user_school pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Run the list_forum_posts pipeline.
| Argument | Type | Description |
|---|---|---|
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
{
"type": "object",
"properties": {
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
}
}
}Clannit auth login (email + password). Returns JWT in step_1_body_data_token. Requires step_1_body_email and step_1_body_password — collect via collect_user_input or emit_display input BEFORE calling this pipeline. Chat/Android sessions do not register push tokens.
| Argument | Type | Description |
|---|---|---|
| step_1_body_email* | string | Clannit account email |
| notification_message | string | Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names. |
| step_1_body_password* | string | Clannit account password |
{
"type": "object",
"required": [
"step_1_body_email",
"step_1_body_password"
],
"properties": {
"step_1_body_email": {
"type": "string",
"description": "Clannit account email"
},
"notification_message": {
"type": "string",
"description": "Short user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names."
},
"step_1_body_password": {
"type": "string",
"format": "password",
"description": "Clannit account password"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 2, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.