Your assistant. Your properties. Your permission.
Use Claude, ChatGPT, Codex or another compatible assistant to understand your listings, stay on top of your properties, and prepare the next step. You choose the account, the permissions and what gets approved.
Open Sales / Leasing Open Property Management
Botway’s remote connection is available. Add it in a compatible assistant and sign in to connect your account.
Custom connections depend on your assistant’s plan, region and workspace settings. These are independently configured integrations, not claims of vendor endorsement or marketplace approval.
Review listing facts, showing activity, current offer terms and transaction progress. Ask your assistant to draft a listing description, showing request or offer response for you to review in Botway.
“Show me the latest offers on my listing and flag the terms that are still missing.”
Find properties in your account, review operating summaries and findings, calculate vacancy costs, or prepare a work order. Brokerage and management permissions are separate.
“Compare the vacancy cost of these lease-up options, using these rent and timing assumptions.”
Proposals go to Botway’s existing approval process. A drafted showing request is not a confirmed appointment. An offer proposal is not an accepted offer. Check the recorded result after review.
You can revoke a connection from either console.
Each compatible client connects to the same Botway server. Your assistant’s connector settings handle its side of the connection.
https://www.botway.ai/api/mcp
Authentication: OAuth. Your Botway password stays with Botway.
Custom connection
Open the custom app or connector settings, add Botway’s server address, and choose OAuth. Sign in to Botway and approve the account and permissions.
Use a workspace or plan that permits custom remote MCP apps. Your workspace administrator may need to enable access.
Official setup documentation ↗Remote MCP
Add Botway as an HTTP MCP server. Start its OAuth sign-in, then review access in Botway.
Use the remote MCP connection settings in your Codex client. Native browser sign-in returns to a local callback.
Official setup documentation ↗Custom connector
In Claude’s connector settings, add a custom remote connector with Botway’s server address. Connect and complete Botway sign-in.
Custom connector availability depends on your Claude account and workspace policy.
Official setup documentation ↗Custom app / developer mode
Where available, add Botway as a custom MCP app in Gemini Developer Mode, then complete OAuth. Gemini CLI can use the same HTTP server and OAuth discovery.
Google documents custom MCP apps and Developer Mode. Access and app review vary by account. Botway is not claiming a Google marketplace listing.
Official setup documentation ↗Custom remote connector
Add a custom remote connector, enter Botway’s server address, select OAuth, and review the requested Botway permissions.
Use an account with custom remote connectors enabled. Organization policies may restrict connections.
Official setup documentation ↗Custom MCP connector
Register Botway’s remote MCP server as a custom connector, choose OAuth, and sign in to Botway.
Custom connectors may require workspace or administrator setup in Mistral’s connector settings.
Official setup documentation ↗Add this to your client’s MCP settings, then run its OAuth sign-in. Approve only the permissions you need.
{
"mcpServers": {
"botway": {
"httpUrl": "https://www.botway.ai/api/mcp",
"oauth": {
"enabled": true,
"scopes": [
"pms:read",
"brokerage:read"
]
}
}
}
}Gemini CLI documentationAccess is limited and expires. Disconnect in Botway at any time. Existing connections keep their original permissions; brokerage access requires a new explicit grant. No connection shares your password or grants an assistant permission to approve its own proposals, sign agreements or transfer money.
How Botway protects your information · Privacy policy · Technical API and agent guide
Separate permissions for listings, showing summaries, offer terms, transaction progress, property summaries, calculations and human-reviewed proposals.
Complete live account tests across supported clients, publish verified setup guides, and pursue provider directory listings where review is required.
Extend duplicate prevention and durable receipts across public inquiries and booking requests. Measure completion, retries and successful human handoffs.
Expand application and lease preparation, document requests and showing coordination through the existing approval and authorization systems.
Evaluate Grok custom MCP and Microsoft Copilot’s supported custom-connector routes. Consumer and business products have different capabilities; availability will be stated explicitly.
Roadmap items describe planned work, not a promise that an integration or workflow is available in every account today.