Setting Up the Streamline VRS Connector

Path: Connectors → Streamline VRS → Configuration

What this connector does

The Streamline VRS connector exposes your vacation rental management data — properties, reservations, owners, work orders, availability, and rates — as an MCP tool. Once configured, your team's AI assistants can answer questions about your portfolio without anyone digging through Streamline's UI.

It also feeds Wazzi's Data Sources page, so Operations Center and Portfolio Center products can keep their dashboards in sync with Streamline on a schedule.

Wazzi authenticates to Streamline using two credentials: an API key and an API secret, both issued by Streamline. They're sent in the body of each request — Streamline's standard auth pattern.

Before you start — getting your Streamline credentials

You'll need an active Streamline VRS account with administrator-level permissions. Streamline doesn't expose API credentials in their public docs — they're issued by Streamline support on request.

1. Sign in to your Streamline VRS admin: https://web.streamlinevrs.com (or your org's specific subdomain).
2. Open a support ticket with Streamline asking for an API key and secret pair for third-party integration. Mention you're integrating with Wazzi MCP.
3. Streamline support will respond with three values:
   • API URL — usually https://web.streamlinevrs.com/api/json, but Streamline may give you a different host for your account.
   • API Key — your account-specific token.
   • API Secret — pairs with the key.
4. Copy all three. Treat the key and secret like passwords — they grant full read access to your Streamline data.

Don't have credentials yet? Streamline's support team typically issues them within 1–2 business days. While you wait, you can still add the connector tile to your catalog without an instance — set it to "Added (Inactive)" and configure the instance later.

What this connector unlocks for your team

Once configured, members with the right MCP permissions can ask Claude / ChatGPT / Cursor things like:

• "List all properties at the Aspen location."
• "Show me reservations for unit 42 next month."
• "Pull up the owner statement for property ID 12345."
• "What work orders are open for the Tahoe portfolio?"
• "Find availability and nightly rates for the Beachhouse next weekend."

The exact set of available actions depends on which MCP toggles you've flipped on for the user's group — see Managing Permissions.

Steps — configuring Streamline in Wazzi

1. From the Connectors catalog, click Configure on the Streamline VRS tile.

You'll land on Streamline's Configuration tab:

2. Fill in the three fields.

• API URL — the host Streamline gave you. Default is https://web.streamlinevrs.com/api/json.
• API Key — paste the key from your support ticket reply.
• API Secret — paste the secret. This will be encrypted at rest.

3. Click Test Connection.

Wazzi makes a low-impact call to Streamline (typically a small property list query) to verify the credentials. Success means you're good to go.

4. Click Save Configuration.

Streamline moves to the Active section of the catalog and the dot turns green.

Troubleshooting

• "Test Connection failed: 401" or "invalid credentials". Key or secret is wrong, expired, or rotated. Re-open your Streamline support ticket and ask them to confirm or reissue.
• "Test Connection failed: 403." Credentials are valid but the user behind them lacks scope. Ask Streamline support to elevate the API user's permissions.
• "Test Connection failed: timeout / DNS." Wrong API URL, or Streamline is down. Verify the URL with support and check https://status.streamlinevrs.com.
• Rate-limit errors. Streamline limits to ~100 requests/minute per token pair. Heavy AI workloads can hit this — pace your prompts or contact Streamline about a higher tier.
• The token worked yesterday and fails today. Streamline rotated it. Get a fresh pair from support and update the connector.

Best practices

• Use a dedicated Streamline API user when possible. If Streamline supports it on your tier, request credentials tied to a service account so revoking access doesn't impact a real human's login.
• Document your Streamline support contact. Save the email thread where credentials were issued — you'll need it for rotation.
• Set a quarterly rotation reminder. Streamline credentials don't expire automatically; quarterly rotation is a healthy cadence.
• Wire Streamline into Data Sources. If you're using Wazzi's Operations Center or Portfolio Center, this connector can power those dashboards. See Configuring Data Sources.

Frequently asked questions

Does Wazzi store the API secret in plaintext?
No. The secret is encrypted at rest with per-org keys and decrypted only at request time.

Can I configure two Streamline accounts?
Streamline is a single-instance connector. If you have two Streamline orgs, pick the primary; cross-org access is rare for most teams.

Will this connector write to Streamline?
Currently the connector exposes read endpoints only (properties, reservations, owners, work orders, availability). Write actions are not yet supported.

How fresh is the data?
Direct MCP tool calls are real-time (subject to Streamline's API rate limits). Data Source-driven dashboards reflect the most recent successful sync — see Configuring Data Sources.

What's next

• Restrict who in your org can invoke Streamline actions: Managing Permissions.
• Use Streamline as a data source for Operations Center / Portfolio Center: Configuring Data Sources.
• Wire Streamline into your AI tool: Connecting Claude or Connecting ChatGPT.