ProhostAI MCP

Live

OAUTH 2.1

PROPERTY OPS

Automation

ProhostAI MCP gives agents authenticated access to your property operations: manage listings and tasks, run cleaning and pricing workflows, and handle guest messaging under the manager's own account.

  • Per-user credentials: each task and pricing change runs as the actual manager, never a shared bot.
  • Encrypted per-tenant vault: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: pre-call scope check, 90-day SIEM-exportable audit chain.
ProhostAI MCP
agent · Acme Q3
Run
Which turnovers need a cleaner assigned before tomorrow's check-ins?
S
prohostaimcp_search_tasks
88ms
ProhostAI agent
5 turnovers tomorrow, 2 without a cleaner. Assigned from the standing roster and added the standard checklist to each.
Tasks: 5 turnovers, 2 assigned
prohostaimcp
5 tasks
18:29
Message Claude...

Tools your operations agent reaches for in ProhostAI, scoped per user.

CALL ANY TOOL
Run property operations end to end: manage places and tasks, build cleaning checklists, set pricing overrides, handle approvals, and coordinate guest messaging.
prohostaimcp_add_cleaning_checklist_item
Add cleaning checklist item
Add a new item to a cleaning checklist.
Parameters
Name
Type
Required
Description
checklist_id
string
Required
The unique identifier of the checklist to add an item to.
cleaning_id
string
Required
The unique identifier of the cleaning job the checklist belongs to.
title
string
Required
The title of the new checklist item.
order
string
Optional
The sort order for this item within the checklist.
photo_required
boolean
Optional
Whether the cleaner must submit a photo to mark this item complete.
reference_photo_url
string
Optional
A reference photo URL showing what this item should look like when done correctly.
prohostaimcp_approve_approval_request
Approve approval request
prohostaimcp_bulk_create_tasks
Bulk create tasks
prohostaimcp_bulk_delete_expenses
Bulk delete expenses
prohostaimcp_bulk_remove_listing_tags
Bulk remove listing tags
prohostaimcp_bulk_update_conversations
Bulk update conversations
prohostaimcp_cancel_scheduled_message
Cancel scheduled message
prohostaimcp_community_list_lounges
Community list lounges
prohostaimcp_create_guidebook
Create guidebook
prohostaimcp_create_task
Create task
prohostaimcp_crm_archive_opportunity
Crm archive opportunity
prohostaimcp_crm_get_opportunity
Crm get opportunity
prohostaimcp_crm_set_custom_field
Crm set custom field
prohostaimcp_delete_expense_category
Delete expense category
prohostaimcp_delete_place
Delete place
prohostaimcp_docs_read
Read docs
prohostaimcp_drive_search
Search drive
prohostaimcp_edit_cleaning_comment
Edit cleaning comment
prohostaimcp_get_guest_custom_fields
Get guest custom fields
prohostaimcp_get_place
Get place
prohostaimcp_list_cleaning_attachments
List cleaning attachments
prohostaimcp_list_place_tags
List place tags
prohostaimcp_message_ai_employee
Message ai employee
prohostaimcp_publish_review_reply
Publish review reply
prohostaimcp_run_workflow
Run workflow
prohostaimcp_send_message
Send message
prohostaimcp_sheets_query
Query sheets
prohostaimcp_update_contact
Update contact
prohostaimcp_update_notification_settings
Update notification settings
prohostaimcp_upload_cleaning_attachment
Upload cleaning attachment

For more tools, view docs.

Build your Agent
Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// ProhostAI tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prohostaimcp"], toolNames: [
    "prohostaimcp_list_places",
    "prohostaimcp_search_tasks",
    "prohostaimcp_list_skills"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Which turnovers need a cleaner assigned before tomorrow's check-ins?" }] });
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prohostaimcp"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Which turnovers need a cleaner assigned before tomorrow's check-ins?" }],
  tools,
});

// Execute the tool call with the user's vaulted ProhostAI credential
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prohostaimcp"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Which turnovers need a cleaner assigned before tomorrow's check-ins?" }],
  tools,
});

// Tool call runs with the user's vaulted ProhostAI credential
await sk.tools.executeTool(msg.content, "user_123");
import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["prohostaimcp"] }, pageSize: 100,
});

const agent = new Agent({
  name: "prohostai_agent",
  model: "gemini-2.5-pro",
  instruction: "Manage ProhostAI for the signed-in user.",
  tools,
});

await agent.run("Which turnovers need a cleaner assigned before tomorrow's check-ins?");
Try these prompts
Copy any prompt into your agent. Each maps directly to a ProhostAI tool. Click to copy, paste into your agent, done.
Turnovers
Copy the prompt
Copied
Which turnovers need a cleaner before tomorrow?
Copy the prompt
Copied
Add the standard checklist to this cleaning task.
Copy the prompt
Copied
Which cleanings are overdue?
Pricing
Copy the prompt
Copied
Set a pricing override for the lake house next weekend.
Copy the prompt
Copied
Which listings have no pricing rule?
Copy the prompt
Copied
Approve the pending pricing change.
Guests
Copy the prompt
Copied
Draft a check-in message for tonight's arrivals.
Copy the prompt
Copied
Which guests have unanswered messages?
Copy the prompt
Copied
Tag this place as pet-friendly.
SEE HOW AUTH WORKS
Your users connect once. Their ProhostAI credentials stay vaulted, every call is scope-checked, and every action is logged.
1
Authorize
Your user connects
ProhostAI MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
ProhostAI MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
ProhostAI MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
ProhostAI MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other automation connectors.
People Ops and HR teams
New Hire Provisioning Agent
Open-source Python template. Creates or detects the hire in Deel, provisions their Workspace account, builds the Notion onboarding page, posts the welcome.
People Ops and HR teams
PTO & Leave Request Agent
Open-source Python template. Resolves the employee in Deel, validates against their real entitlement, submits the request for approval, blocks the calendar.
Engineering Teams
Incident Response Agent
Open-source Python template. Triggers the PagerDuty page, opens the Jira incident, notifies the on-call Slack channel, and drafts the Confluence postmortem.
GTM and RevOps Teams
Competitive intelligence briefing agent
Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.
Test other agents
See the same per-user auth pattern across other automation connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Slack workflow agent (LangGraph)
LangGraph agent that drives multi-step Slack workflows: triggers, approvals, and follow-up actions per user identity.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared keys blur who changed what
A shared ProhostAI token looks fine in a demo. In production every pricing override and guest reply looks like one integration, and you cannot tell which manager acted. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
ProhostAI today. Ten connectors tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access ProhostAI as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the ProhostAI OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in ProhostAI?
Yes. Pass a tool name filter to listScopedTools so the automation agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches ProhostAI.

What happens when a user revokes ProhostAI access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the agent respect ProhostAI permissions?
Yes. Every call runs as the authorizing user. Native roles, sharing settings, and scope restrictions in ProhostAI apply to each request, and actions log to the audit chain.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""prohostaimcp"": {
""url"": ""https://mcp.scalekit.com/prohostaimcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.prohostaimcp]
url = ""https://mcp.scalekit.com/prohostaimcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""prohostaimcp"": {
""url"": ""https://mcp.scalekit.com/prohostaimcp"",
""type"": ""http""
}
}
}